Closed Roguelazer closed 11 years ago
I just got the same traceback. Python doc says this: http://docs.python.org/library/logging.html#thread-safety
I'll take this issue and try a fix with a custom logging handler.
This should be fixed, with merge #46. Closing.
I've seen a few times where a zygote will get "stuck" waiting on the logging semaphore. I thing it might be a signal issue, but I'm not positive. The top of the stack trace looks like:
and the next interesting part is at
This should be treated as P0, since it can prevent zygote from switching over on version changes.
Pretty easy to repro. Just keep starting up a simple zygote-using application and ctrl-cing it until you get an error binding to port.
I have only observed the zygote itself getting blocked (not the worker processes or the master). That is only anecdotal, though.