Hello all:
Before I begin slicing my code apart in an effort to isolate my memory leak, I thought I'd ask if there were "typical" ways that new wxPython programmers leak ... memory, that is. Any thoughts would be greatly appreciated.
Mark
Here is the message I get upon closing the program:
11:22:22 AM: There were memory leaks.
11:22:22 AM: ----- Memory dump -----
11:22:22 AM: wxEvtHandler at $1507868, size 48
11:22:22 AM:
11:22:22 AM: ----- Memory statistics -----
11:22:22 AM: 1 objects of class wxEvtHandler, total size 48
11:22:22 AM:
11:22:22 AM: Number of object items: 1
11:22:22 AM: Number of non-object items: 0
11:22:22 AM: Total allocated size: 48
11:22:22 AM:
···
_________________________________________________________________
Chat with friends online, try MSN Messenger: http://messenger.msn.com
Thanks for the good news! And is it possible that my frequent program crashes are also due to these memory leaks?
Luc
···
At 09:53 1/02/2002 -0800, Robin Dunn wrote:
> Hello all:
> Before I begin slicing my code apart in an effort to isolate my memory
leak,
> I thought I'd ask if there were "typical" ways that new wxPython
programmers
> leak ... memory, that is. Any thoughts would be greatly appreciated.
>
> Mark
>
> Here is the message I get upon closing the program:
>
> 11:22:22 AM: There were memory leaks.
> 11:22:22 AM: ----- Memory dump -----
> 11:22:22 AM: wxEvtHandler at $1507868, size 48
If you're using a wxGrid then this is a known bug, and you can just ignore
it for now.
--
Robin Dunn
Software Craftsman
robin@AllDunn.com Java give you jitters? http://wxPython.org Relax with wxPython!
thanks for your consideration. Yes, i should try to reproduce such crashes in a small sample.
But for the moment i cannot even reproduce them systematically in my complete application! They just happen "quite often", and i cannot see any rule. Yesterday morning i almost thought i had found a reason for such crashes: by modifying the python source code while the application is still running. This worked twice, but when trying to reproduce it a third time, the error failed...
I must say that for the moment my application itself is not very stable, so for the moment i don't care too much about those crashes. Let's wait and see. You will hear from me if i got one.
Luc
···
At 11:59 4/02/2002 -0800, Robin Dunn wrote:
>
> Thanks for the good news! And is it possible that my frequent program
> crashes are also due to these memory leaks?
Probably not. Can you duplicate your crashes in a small sample to send
here?
--
Robin Dunn
Software Craftsman
robin@AllDunn.com Java give you jitters? http://wxPython.org Relax with wxPython!
thanks for your consideration. Yes, i should try to reproduce such crashes
in a small sample.
But for the moment i cannot even reproduce them systematically in my
complete application! They just happen "quite often", and i cannot see any
rule. Yesterday morning i almost thought i had found a reason for such
crashes: by modifying the python source code while the application is still
running. This worked twice, but when trying to reproduce it a third time,
This is no problem, btw. Python executes its pyc|pyo files, not the source
itself, unlike shell scripts and the like
the error failed...
I must say that for the moment my application itself is not very stable, so
for the moment i don't care too much about those crashes. Let's wait and
see. You will hear from me if i got one.
Good luck
Hans-Peter
···
On Tuesday, 5. February 2002 23:39, Luc Saffre wrote:
Luc
At 11:59 4/02/2002 -0800, Robin Dunn wrote:
> > Thanks for the good news! And is it possible that my frequent program
> > crashes are also due to these memory leaks?
>
>Probably not. Can you duplicate your crashes in a small sample to send
>here?
>
>--
>Robin Dunn
>Software Craftsman
>robin@AllDunn.com Java give you jitters?
>http://wxPython.org Relax with wxPython!