Message211436
| Author |
itamarst |
| Recipients |
JohanAR, itamarst, sbt |
| Date |
2014年02月17日.18:50:43 |
| SpamBayes Score |
-1.0 |
| Marked as misclassified |
Yes |
| Message-id |
<1392663043.65.0.517457527868.issue14976@psf.upfronthosting.co.za> |
| In-reply-to |
| Content |
This is not specifically a signal issue; it can happen with garbage collection as well if you have a Queue.put that runs in __del__ or a weakref callback function.
This can happen in real code. In my case, a thread that reads log messages from a Queue and writes them to disk. The thread putting log messages into the Queue can deadlock if GC happens to cause a log message to be written right after Queue.put() acquired the lock.
(see https://github.com/itamarst/crochet/issues/25). |
|
History
|
|---|
| Date |
User |
Action |
Args |
| 2014年02月17日 18:50:43 | itamarst | set | recipients:
+ itamarst, sbt, JohanAR |
| 2014年02月17日 18:50:43 | itamarst | set | messageid: <1392663043.65.0.517457527868.issue14976@psf.upfronthosting.co.za> |
| 2014年02月17日 18:50:43 | itamarst | link | issue14976 messages |
| 2014年02月17日 18:50:43 | itamarst | create |
|