noreply at rubyforge.org
2007-Jul-27 00:29 UTC
[wxruby-development] [ wxruby-Bugs-12610 ] Possible crash with EvtHandler.add_pending_evemt and custom event class
Bugs item #12610, was opened at 2007-07-27 00:29 You can respond by visiting: http://rubyforge.org/tracker/?func=detail&atid=218&aid=12610&group_id=35 Category: Incorrect behavior Group: None Status: Open Resolution: None Priority: 2 Submitted By: Alex Fenton (brokentoy) Assigned to: Alex Fenton (brokentoy) Summary: Possible crash with EvtHandler.add_pending_evemt and custom event class Initial Comment: If a custom event sets associated client_data using set_client_data, and then the event is queued using EvtHandler#add_pending_event the client_data may be prematurely deleted if GC runs before the event is actually processed. Temporary workaround is to send the event for immediate processing via process_event. ---------------------------------------------------------------------- You can respond by visiting: http://rubyforge.org/tracker/?func=detail&atid=218&aid=12610&group_id=35
Maybe Matching Threads
- [728] trunk/wxruby2/Changelog: HTML classes, Window[ChangeDestroy]Event, sample fix, client_data
- [766] trunk/wxruby2: Added item_data aliases for client_data functions, update doc & tests;
- [1061] trunk/wxruby2/swig/classes/EvtHandler.i: Remove a lot of no longer needed includes from EvtHandler.i
- [1075] trunk/wxruby2/lib/wx/classes/evthandler.rb: Send IconizeEvent to EvtHandlers
- [1096] trunk/wxruby2/lib/wx/classes/evthandler.rb: Add mapping for another obscure and undocumented event type