I was just going through _speedups.c line by line just out of curiosity. The only thing I could find was a missing Py_DECREF(format) at the end of Markup_repr(), which I'm pretty sure should be there. But I hardly think that's anywhere near related to THE memory leak.
Erik On Feb 1, 2008 9:17 PM, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote: > > was the behaviour the same with and without speedup? i was just > thinking on http://genshi.edgewall.org/changeset/781. you also > remarked earlier "..not be surprised if it's some of the more > expensive versioncontrol pages". what change from 0.10.4 to 0.11 were > you thinking of ? > > rupert. > > On Jan 9, 9:22 pm, Jonas Borgstr�m <[EMAIL PROTECTED]> wrote: > > Jeroen Ruigrok van der Werven wrote: > > > > > > > > > -On [20080109 16:56], David Abrahams ([EMAIL PROTECTED]) wrote: > > >>I think we already found and submitted a patch for this problem: > > >>http://trac.edgewall.org/ticket/6581 > > > > > It's in trunk now, r6385. > > > > > Perhaps Noah and Jonas can also give this latest trunk a spin and see how > > > it > > > handles itself. > > > > Just for the record: I tested latest trunk again but didn't notice any > > improvement. This time there was more traffic on the server than last > > week so it didn't take longer than about 30 minutes for the server to > > start running out ofmemory. When I aborted this experiment each fcgi > > process was using about 3 times more residentmemory(325MB) compared to > > > 0.10.x (around 100MB after running for a week). > > > > Cheers, > > Jonas > > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Trac Development" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/trac-dev?hl=en -~----------~----~----~----~------~----~------~--~---
