Some updates on the elusive #6614 bug Jeroen Ruigrok van der Werven wrote: >>> I mean, might it make sense to release 0.11.0 now to get the release out the >>> door and continue to look for these more elusive cases for a 0.11.1 release? >>> >> Well, it's a more a matter of fixing the Genshi issue for 0.5, then make >> Trac 0.11 depend on that version. As I said in the comment:38 (linked >> above), 0.4.x has the #G158 bug which makes Trac unreliable in >> multithreaded setup, so I wouldn't recommend using it. >> > > Ok, but then releasing Genshi 0.5 becomes a blocking priority before > releasing Trac 0.11, since we need to get the eggs, especially for Windows > with speedups, out there. >
Thanks to Alec who managed to write a Genshi-only test program exhibiting the problem, we could narrow down the specific issue about the memory constantly growing when an exception was raised from a template to a Genshi bug. Well, I have the feeling it must rather be a Python bug, but at least it's triggered at (and can be worked around at) the Genshi level. See #G190. But that issue is not the only problem we have w.r.t. to high memory usage. I think it's still relatively easy to make the memory usage grow to a high number where it will stay forever, even with Python 2.5. That has to be improved further. >>> I am just trying to get a sense of the choice between finally releasing 0.11 >>> and stability for the end-users. >>> >> Perhaps we can make another beta after the two patches on #6614 (listed >> in 1. and 2.a above) are committed, and see how things work in practice? >> > > Sure, I think our encountered issues warrant another beta regardless. > > The current state of affair is however quite better than it used to be, so we can probably prepare a beta2 even if #6614 is not completely fixed at this point. Thoughts? -- Christian --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Trac Development" group. To post to this group, send email to trac-dev@googlegroups.com 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 -~----------~----~----~----~------~----~------~--~---
