On Aug 22, 2007, at 11:00 AM, morgamic wrote:
> > On Aug 18, 11:09 am, Ben Bangert <[EMAIL PROTECTED]> wrote: >> Forgot to ask, what version of Beaker are you using? > More version info: > Beaker-0.7.3 > python-psycopg2-2.0.4-1.el5.rf > > So far I've been unsuccessful in finding the leak -- but the main > issue is this page in list(): > http://socorro.googlecode.com/svn/trunk/webapp/socorro/controllers/ > report.py > > Do you have any pointers on how do debug memory leaks? > What o/s are you using? First of all, ensure you're not using an older version of Python, there were a couple of leaks in older versions. (Latest 2.4.4/2.5.1 should be fine). I'd also upgrade Beaker just in case. Did you investigate the psycopg memory leak? Maybe Uwe could point us to where that was reported (I couldn't find it). Are you using the gc module for for debugging? If not: It can be set to print verbose gc messages via gc.set_debug There's a gc.DEBUG_LEAK setting you can use, but I've found gc.DEBUG_SAVEALL is only useful in certain situations, so you might want to start out with: gc.set_debug(gc.DEBUG_LEAK & ~gc.DEBUG_SAVEALL) Then you could create a simple controller that does a gc.collect(), and prints out the contents of gc.garbage. -- Philip Jenvey --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "pylons-discuss" 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/pylons-discuss?hl=en -~----------~----~----~----~------~----~------~--~---
