[ wxwindows-Bugs-1523301 ] wxEventLoop leaking memory

SourceForge.net noreply at sourceforge.net
Sun Jul 16 00:30:23 PDT 2006


Bugs item #1523301, was opened at 2006-07-16 09:30
Message generated for change (Tracker Item Submitted) made by Item Submitter
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=109863&aid=1523301&group_id=9863

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: Thread
Group: Must fix
Status: Open
Resolution: None
Priority: 5
Submitted By: Steven Van Ingelgem (g00fy)
Assigned to: Nobody/Anonymous (nobody)
Summary: wxEventLoop leaking memory

Initial Comment:
evtloop.cpp @ 260: a new message is created in case of 
a message coming in when it's not in the main thread.

Now if this message is for example close (like in my 
case), it gets stuck in the locally defined static 
variable 's_aSavedMessages'.

It will be freed by the OS ofcourse, but it's not a 
very clean solution imho.


Greetings,
Steven

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=109863&aid=1523301&group_id=9863




More information about the wx-dev mailing list