• Advertisement
Sign in to follow this  

What would cause an app to stay in the task manager after it is destroyed?

This topic is 2981 days old which is more than the 365 day threshold we allow for new replies. Please post a new topic.

If you intended to correct an error in the post then please contact us.

Recommended Posts

Some weird behaviour is happening in one of my apps. All it is, is an app that creates a window, and calls postquitmessage() when ever WM_DESTROY or WM_CLOSE are found. The weird thing is the app closes just fine, except it still is running. It's in task manager still, so it must be staying alive some how. I've googled and just can't find anyone else with this happening to them.

Share this post


Link to post
Share on other sites
Advertisement
Quote:
Original post by KrazeIke
This thread may be relevant. However, if that's all your program does, then it's probably easier to just post your code than having us speculate.


Thank you. that post was very hepful. I changed peekmessage, so that I passed a NULL handle instead and it works like normal now, weird thing is the exact same code in a different project doesn't give the same results?? I would post the code but it's split into different classes and might be hard to read for something so short.

Share this post


Link to post
Share on other sites
I assume you're returning a value of 0 after calling PostQuitMessage().

Share this post


Link to post
Share on other sites
Sign in to follow this  

  • Advertisement