Solved

Problem with the message pump hanging

Posted on 1997-08-29
3
546 Views
Last Modified: 2013-12-03
I have a very strange problem. I am working with an application that
uses many different threads. At some point I seem to get into a
situation where there are no threads to pump the message queue. The code
in question create an event and posts a WM_USER style message to the
window queue and then does a WaitForSingleObject(). The message pump is
supposed to see the message and post the event to cause the wait to
finish. The problem appears to be that the thread that is supposed to be
pumping is the one waiting. I tried using WaitForMultipleObjects() and
dispatching the messages myself but that also doesn't seem to work.
I am looking for any other clues that prople might be able to give me.

The purpose of this logic is to insure that the message queue is empty
before killing the window. The processing must be synchonous. I don't think I can allow the window to
go down asynchronously
0
Comment
Question by:sasjaa
  • 2
3 Comments
 
LVL 3

Expert Comment

by:vinniew
ID: 1405120
You shouldn't do it like that.  It's much easier to control if you use a global flag (bool) variable to control things like that.  As for checking the queue before you 'kill' the process, I think you should use Mutexes (see CreateMutex) instead of events.  The event processing is what's causing problems.  You can use mutexes in the same way, but they work inside the main process.

In any case, I can't be sure about this solution without seeing code or without a general outline of what's happening, so post more if you need more.
0
 

Author Comment

by:sasjaa
ID: 1405121
I don't see how a Mutex can help. A window destroy request comes in and we need to make sure that there are no pending messages in the queue for this window before we delete the object. Microsoft documentation clearly states that a CEvent should be used if we must wait for something else to happen before continuing. The problem is that we are waiting on messages and there seems to be nothing to process the messages.
0
 
LVL 3

Accepted Solution

by:
vinniew earned 200 total points
ID: 1405122
You could start up another message 'pump within a pump' to handle the wm_destroy message.  Use the while.. peekmessage.. sendmessage... loop in the handler for wm_destroy.  That would definitely empty the queue.

V
0

Featured Post

Online Training Solution

Drastically shorten your training time with WalkMe's advanced online training solution that Guides your trainees to action. Forget about retraining and skyrocket knowledge retention rates.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

This article shows how to make a Windows 7 gadget that extends its U/I with a flyout panel -- a window that pops out next to the gadget.  The example gadget shows several additional techniques:  How to automatically resize a gadget or flyout panel t…
zlib is a free compression library (a DLL) on which the popular gzip utility is built.  In this article, we'll see how to use the zlib functions to compress and decompress data in memory; that is, without needing to use a temporary file.  We'll be c…
This is Part 3 in a 3-part series on Experts Exchange to discuss error handling in VBA code written for Excel. Part 1 of this series discussed basic error handling code using VBA. http://www.experts-exchange.com/videos/1478/Excel-Error-Handlin…
Email security requires an ever evolving service that stays up to date with counter-evolving threats. The Email Laundry perform Research and Development to ensure their email security service evolves faster than cyber criminals. We apply our Threat…

756 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question