I’ve been working on an app for 3 months now, I create a destroy lots of wxStyledTextCtrls on Notebook pages. When I open a few, memory gets allocated, never released.
wxWindows has this wxDebugContext class, I can’t seem to find it in wxPython. Is there an equivelant? I need to find what is really causing this memory bloating, it has made my app unusable and I must deliver to clients by this weekend
I tried calling Destroy() on each control, I even tried printing the variable afterwards and it says the C++ part of this object has been deleted, but the memory it still chomped.
I’m creating a context menu for the wxStyledTextCtrl, it needs to be deleted explicitly since popup menus are do not have a parent frame that takes care of deleting it.
Thx all.
···
On Thu, 2002-12-19 at 22:57, Ahmad Baitalmal wrote:
*Hi,
I’ve been working on an app for 3 months now, I create a destroy lots of wxStyledTextCtrls on Notebook pages. When I open a few, memory gets allocated, never released.
wxWindows has this wxDebugContext class, I can’t seem to find it in wxPython. Is there an equivelant? I need to find what is really causing this memory bloating, it has made my app unusable and I must deliver to clients by this weekend
I tried calling Destroy() on each control, I even tried printing the variable afterwards and it says the C++ part of this object has been deleted, but the memory it still chomped.
What am I missing here?
Thanks*
I this I got it,
I'm creating a context menu for the wxStyledTextCtrl, it needs to be deleted explicitly since popup menus are do not have a parent frame that takes care of deleting it.
Yes. Also dialogs need to be explicitly destroyed.
···
--
Robin Dunn
Software Craftsman http://wxPython.org Java give you jitters? Relax with wxPython!
