[wxpython-users] bogus timer id in wxTimerProc
Robin Dunn
robin at alldunn.com
Mon Sep 8 12:36:55 PDT 2008
Mark Guagenti wrote:
> I'm curious about what the following error means:
> PyAssertionError: C++ assertion "node != TimerMap().end()" failed at
> ..\..\src\msw\timer.cpp(158) in wxTimerProc(): bogus timer id in
> wxTimerProc
>
>>From the little I could learn about this error from searching around
> it seems like this might happen if a timer is started from a different
> thread.
>
> I'm seeing in this on Windows XP with wxPython 2.8.7.1
>
> Anyone else have any light they could shed on what would generate this
> assertion?
Another possibility is that there is a timer event already in the queue
when the timer is destroyed. When the event is then processed the main
timer WinProc is called and it tries to find info about the timer from
the ID so it can dispatch the wx event, but the id is no longer in the
hash map.
--
Robin Dunn
Software Craftsman
http://wxPython.org Java give you jitters? Relax with wxPython!
More information about the wxpython-users
mailing list