#2913: Memory Leak on SVN Repo Access using tracd or WSGI
---------------------------------------+------------------------------------
Reporter: edsuom | Owner: jonas
Type: defect | Status: new
Priority: high | Milestone:
Component: browser | Version: devel
Severity: major | Resolution:
Keywords: wsgi, tracd, memory, leak |
---------------------------------------+------------------------------------
Changes (by edsuom):
* keywords: => wsgi, tracd, memory, leak
Comment:
I spent a lot of time today trying to resolve this problem by caching
instances
of {{{trac.versioncontrol.svn_fs.Pool}}} but am abandoning the effort for
two
reasons:
* It only helped keep new instances of {{{libsvn.core.apr_pool_tPtr}}}
from
being constructed on page reloads. The other offending {{{libsvn}}}
objects
multiplied like rabbits just as before.
* The caching is broken; I couldn't figure out how to fully account for
{{{Pool}}} instances that were no longer valid.
I've attached the patch for possibly historical interest, but don't
recommend
trying to use it.
I've done everything I'm capable of on this ticket and request that
someone
'''please''' take it on and fix it so I can continue with my WSGI trac
deployment. Thanks!
--
Ticket URL: <http://projects.edgewall.com/trac/ticket/2913>
The Trac Project <http://trac.edgewall.com/>
_______________________________________________
Trac-Tickets mailing list
[email protected]
http://lists.edgewall.com/mailman/listinfo/trac-tickets
