#2913: Memory Leak on SVN Repo Access using tracd or WSGI
---------------------------------------+------------------------------------
Reporter: edsuom | Owner: jonas
Type: defect | Status: new
Priority: high | Milestone: 0.10
Component: browser | Version: devel
Severity: major | Resolution:
Keywords: wsgi, tracd, memory, leak |
---------------------------------------+------------------------------------
Comment (by mgood):
Well, I'm glad the caching has made Trac usable for you, but it seems like
it's really only slowing the leak, not a "fix". Maybe it's unavoidable,
but I think it could use some more investigation.
Also, when submitting patches please try to follow TracDev/CodingStyle.
In particular, Trac uses the `lowercase_with_underscores` for functions,
variables and class members. I made some changes to the patch to follow
the conventions, and keep the `Pool.__init__` arguments ordered so that
it's backwards-compatible. It's not quite working, but I figured I'd hold
off on fixing it since I'd like to get some other opinions on whether
caching is the best solution.
--
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
