On Mon, Jan 29, 2007 at 02:26:52PM -0700, Jack Moffitt wrote: > We've been having a severe lag problem at Chesspark that we've been > slowly tracking down over the last month. It was hard to find because > it only happened in long running instances, and never happened in our > test cases. > > [..]
Yes. This is a known issue: http://twistedmatrix.com/trac/ticket/1652. > Attached is a very small patch that fixes this problem as long as a > response is received for the IQ stanza. If no response is received, > it still leaks, but I understand this is fixed by t.w.p.j.xmlstream.IQ > using a timeout. We'll switch to that soon, but this patch will help > others who haven't. The patch I attached there is more or less the same, but I should look into the issue that Christopher mentions. It'd be nice to follow up via the ticket. > I would appreciate if someone could add documentation that it still > leaks in this case, but shouldn't be a problem in general. When I commit this patch, I will add documentation. In general I would like to mention that filing a ticket in Trac for problems like this makes it easier for me to keep a tab on things that need to be done. On the other hand, for questions or discussion about anything related to the Jabber bits in Twisted this is the preferred forum. I appreciate the recent message increase on this list, so keep that up. Also, I'd like to point out some of the developments I've been working on in my sandbox [1], the XMPP subprotocols branch [2] and the S2S branch [3]. If anyone would care to take a look and see how those things affect them, that'd be great. [1] http://twistedmatrix.com/trac/browser/sandbox/ralphm [2] http://twistedmatrix.com/trac/browser/branches/xmpp-subprotocols-2178-2 [3] http://twistedmatrix.com/trac/browser/branches/xmpp-s2s-2320 Not that branches have a ticket number encoded in them, too. -- Groetjes, ralphm _______________________________________________ Twisted-Jabber mailing list [email protected] https://mailman.ik.nu/mailman/listinfo/twisted-jabber
