On Jul 13, 2009, at 1:34 PM, Lukasz Szybalski wrote:
> Hello, > > Trac installed: June 17th (1 month ago) > Trac version:0.11.1 > Trac tickets: 13083 (503 tickets per day on average) > > Trac started with the following command: > tracd -p 8080 --basic-auth=*,/usr/local/bin/.htpasswd,/usr/local/bin/ > trac > /usr/local/bin/trac > > Current memory usage:44.8% ~450mb > > Any idea of known memory leaks ? I have not seen problems until > overall system performance decreasing slowly and users notifying me of > delayed ticket uploads via xmlrpc. > > I will restart the service soon, but I figured I can provide some > debug information for anybody that is interested if you tell me (copy > paste) what needs to be done? > > How can I debug this memory issue? I haven't got much problems with memory leak using trac, maybe you should first try to update you python, database drivers, svn bindings and then trac itself. On a dev machine of course :). I think you can use dtrace if on osx or solaris to see memory allocation in the python interpreter, maybe there is something like that on linux. Or you could try to run tracd on valgrind. -- Leonardo Santagada santagada at gmail.com --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Trac Users" 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-users?hl=en -~----------~----~----~----~------~----~------~--~---
