Re: PostMessage and unprocessed messages
"Joseph M. Newcomer" <newcomer@flounder.com> ha scritto nel messaggio
news:p9k6t3l5rfdc1mejdc6qi7d4lneo7ig5tf@4ax.com...
Even if there are message pending, calling the MemoryMgr destructor or
Clear
method deletes all pending heap pointers.
The key here is that memory management is centralized into this class.
****
So what, exactly, does this accomplish, other than adding gratuitous
complexity to a
simple program?
The sender (worker thread) allocates dynamic data and puts a pointer in
LPARAM.
If the message is processed by GUI thread, the receiver does a delete of
that pointers.
The problem is that if there are pending non-processed messages, there are
memory leaks.
I need to do, when dialog closes: "Remove all message data pointers
allocated in the heap". I can do that with the centralized memory manager.
The other approach is WFSO with PeekMessage message pump to process pending
messages just deleting heap memory.
BTW: I've also tested creating some data using new BYTE[ 20000000 ] and
*not* deleting[] them... Windows does proper cleanup when the process
terminates, so it seems that no memory is leaked when process exits. So
also
C++ has a kind of built-in (primitive) garbage collector :)
***
The statement of the problem makes no sense. It is IMPOSSIBLE to "leak"
memory after a
process exits because the process has exited, and therefore occupies no
memory!
Before I did this experiment, I may have thought that memory remained
allocated.
I learned that with this experimentation, and now I'm sure about that.
Giovanni