Re: PostMessage and unprocessed messages
Hmmm. Sorry, I didn't understand what you were doing. I've done that kind
of thing as well, but since the memory is allocated couldn't you just
process each of the pending messages and (after flagging that they are no
longer really active) just let the routine that is handling the messages
delete the appropriate data and ignore it otherwise? How many unprocessed
messages are possibly still in the queue. Could you use and OnIdle() loop
to wait until the messages are all received before exiting? Or, does it
really matter since when you exit all pending messages an allocated memory
will just be reclaimed anyway?
Tom
"Giovanni Dicanio" <giovanni.dicanio@invalid.com> wrote in message
news:O8P%23wRHgIHA.3400@TK2MSFTNGP03.phx.gbl...
Hi Tom,
my problem is that I'm having pending messages sent from the background
worker thread to the main GUI thread (dialog-box).
These messages are carrying dynamically allocated data, that I must delete
if I don't want memory leaks.
If these pending messages required no deletion of dynamically allocated
data, I would be happy to just discard and ignore them, but I must process
them (also if the thread has finished its lifetime) just to call delete on
the pointer stored in LPARAM.
Having the boolean signaling the thread is done is one part of the job,
but there is more.
In fact, in the WMU_WORKER_PROGRESS custom message handler, I can do
void OnWorkerProgress( ... )
{
MessageData * data = (MessageData)lParam;
if ( thread is alive )
{
... process data
}
// Delete dynamically allocated data (created using 'new' by the
worker thread)
delete data;
}
I don't want non-processed pending WMU_WORKER_PROGRESS messages in the
message queue, because this would mean leaking memory allocated by the
worker thread.
G