[wxPython] Deletion of wxTimer objects

wxPython Users
1

Deletion of wxTimer objects

Hi again.

I have an application with an instance of a class derived from

wxTimer. It works great, except for the fact that it is never

deleted. I’ve run bunches of experiments and am sure that my

code is not referencing the object anywhere and would expect it

to get garbage-collected. However, when I exit the app I get

a message pointing out that this timer object is a memory leak.

Any help greatly appreciated!

···

Jeff Kotula Sr. Principal Software Engineer

Vital Images jkotula@vitalimages.com

Renunciation is not giving up the things of this world,

but accepting that they go away.

            -- Suzuki Roshi
2

I have an application with an instance of a class derived from
wxTimer. It works great, except for the fact that it is never
deleted. I've run bunches of experiments and am sure that my
code is not referencing the object anywhere and would expect it
to get garbage-collected. However, when I exit the app I get
a message pointing out that this timer object is a memory leak.

Part of the changes done for OOR caused a reference cycle in timers if you
derive from wxTimer and use the Notify method in the derived class. A
workaround is to not do a derived class and use an EVT_TIMER event instead.
See the wxTimer sample in the demo for an example.

···

--
Robin Dunn
Software Craftsman
robin@AllDunn.com Java give you jitters?
http://wxPython.org Relax with wxPython!