From: Kevin A. <al...@se...> - 2004-04-26 00:02:46
|
On Apr 25, 2004, at 7:39 AM, Arthur Elsenaar wrote: > Hi, > > I let codeEditor sit idle overnight and it took more than 500MB of > RAM.. > looking at it using 'top' it shows grabbing ~100k every ~10 seconds! > > OS X 10.3.3, Apple's Python, wxPython 2.5.2.5 panther and PythonCard > 0.7.3.1 > > If it is a wxPython issue, I read wxPython has been substantially > improved in CVS, does it address the leak? > > Thanks, Arthur. > Thanks for the report. Sadly, this is not something I can pin on wxSTC or wxPython. It appears that we have some circular references with the event objects that we use to handle dispatch. I tested with PythonCardPrototype and wxPython 2.4.2.4 as well as PythonCard with 2.5.1.5 on Win2K and Mac OS X and saw the same kind of behavior. The memory leak is very apparent with the codeEditor because it generates "idle" messages almost continuously. However, the leak is definitely there with other samples. Anyway, Rowland and I will investigate and see if we can narrow it down this week. I haven't done much of this kind of memory leak debugging with Python before. I started looking at the gc module, but would appreciate recommendations on tools, code snippets, things to try in the shell, etc. to help pinpoint the problem. I'm sure some of the other developers on this list have far more experience than I. http://docs.python.org/lib/module-gc.html Thanks, ka |