When I use the SendMessage
function with HWND_BROADCAST
, the application hangs up. There is no response from the application for long time.
Can anyone explain why?
This will happen when there is an process that has a top level window, but isn't calling GetMessage or PeekMessage on the thread that created the window.
For backward compatibility with Windows 3.0, SendMessage will not return until all of the top level windows in the system have responded to your broadcast. This behavior made sense back before Windows was multithreaded, because SendMessage(), even when sending to other processes would never block.
But beginning with Win32, when you SendMessage to a window in another process, what actually happens is your thread blocks until the thread in the other process wakes up and handles the message. If that thread is busy, or just not pumping messages, then you wait forever.
For that reason you should always use SendNotifyMessage
or SendMessageTimeout
when you use HWND_BROADCAST, or are otherwise sending messages to windows owned by other processes.
This is because when SendMessage
is called with HWND_BROADCAST
, it first enumerates all the windows available and then calls SendMessage
for each of those windows. SendMessage
will not return until the window has finished processing the message. If a single window is taking a long time to process the message, the entire call will be delayed.
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With