<html><head></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><br><div><div>On May 11, 2010, at 8:28 PM, CARSON DEAN FENIMORE wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite"><span class="Apple-style-span" style="border-collapse: separate; font-family: 'Bitstream Vera Sans Mono'; font-size: medium; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: 2; text-indent: 0px; text-transform: none; white-space: normal; widows: 2; word-spacing: 0px; -webkit-border-horizontal-spacing: 0px; -webkit-border-vertical-spacing: 0px; -webkit-text-decorations-in-effect: none; -webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px; "><span class="Apple-style-span" style="font-family: monospace; ">Just FYI: The problem appears to have gone away with some minor<br>changes. We have twisted in use in a large application, which<br>consists of many threads. These threads were invoking some<br>twisted-related methods; for example, calling addCallback on a<br>Deferred instance from one thread, while running a deferredGenerator<br>in twisted -- this, of course, is not thread safe! Except for a<br>handful of such cases, we were using twisted correctly - adding<br>callbacks on the main thread solved the issue at hand.<br></span></span></blockquote></div><br><div>Glad you solved your problem, and thanks for reporting your conclusions here so future readers don't have to wonder what the heck was going on! :)</div></body></html>