Jason Madden

There's lots of information missing here, so I'm going to have to make some guesses. It seems like what you're saying is that if your server loop never attempts to...

> So, what debug information could help? In general, simplifying to a [short, self contained example](http://sscce.org) is a necessary prerequisite. Assume I know nothing about flask or Werkzeug or the...

Thanks for the report! It can indeed have unexpected consequences to forget to `close()` gevent objects. (`Timeout` [does document this](http://www.gevent.org/api/gevent.timeout.html), but the wording could be stronger.) Running with `GEVENT_DEBUG=debug` or...

The file descriptor you're looping on is effectively *always* ready to read, so you never yield to the event loop (there's never any need to go to a `select()` to...

> @jamadden I disagree. I have had several servers working with pipes and FIFOs assigned to subprocess' FDs and those FDs are not always ready to read if they are...

A core dump isn't going to be much help, I'm afraid. A full traceback might be a bit more helpful, but it looks like there might be something like a...

What's the stack trace? EDIT: Oh, wait, is that what the thing with periods and >> stuff is supposed to be? It's not clear.

It looks like something might have destroyed the hub with [`hub.destroy()`](http://www.gevent.org/api/gevent.hub.html#gevent.hub.Hub.destroy).

It takes an explicit call to `hub.destroy()` to destroy the hub. In the main thread, client code (i.e., you) would have to do that. Threads from the gevent threadpool automatically...

I think (without much evidence, granted) that most use of gevent is via monkey-patching, as that's one of its main advantages (it makes standard code "just work"). gevent tries to...