Solved

Program Crash When Program minimized

Posted on 2007-04-06
4
482 Views
Last Modified: 2013-12-14
I have a C++ MFC application.  I recently started having the following problem: if I leave it running in the background (minimized ) for 10 or 15 minutes, when I eventually come back to it (select it in the taskbar), my application's windows draw very strangely, and the program crashes. By "strange", I mean that the windows that should be positioned at the bottom of the screen draw at the top, but without borders, when I select menu items, a dialog displays with another window inside it (that isn't supposed to be there), etc.  I get assert error messages also.  

I must note that this problem does NOT happen if I leave my application running and keep it in focus (ie, I DON'T minimize it).

Any help would be greatly appreciated.

0
Comment
Question by:clintMon
[X]
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
  • 2
4 Comments
 
LVL 4

Accepted Solution

by:
bikvi_sibro earned 250 total points
ID: 18864414
The first thought that comes to mind is that it might be a refresh issue.  Try running the debugger through the refresh process and see what happens when it is trying to restore itself.
0
 

Author Comment

by:clintMon
ID: 18864602
When you say "refresh process", what specifically do you mean?  Window redrawing?  OnSetActive() routines?
0
 
LVL 8

Assisted Solution

by:mxjijo
mxjijo earned 250 total points
ID: 18865256

Apparently its is hard to say what causing it. You should try to narrow down the problem.
Pls tell us as many details as possible.

1) What does this application do  ?
2) What is the earliest point you got the prob ?
3) Are you doing any large memory handling ?
4) What does the ASSERT say ?
You should be attaching the debugger when the assert/crash happens and  
0
 
LVL 8

Expert Comment

by:mxjijo
ID: 18865281
oops.. hit submit by mistake ..

You should be attaching the debugger when the assert/crash happens and  check the stack trace.
5) As bikvi_sibro suggested, start the app from the debugger and see what happens.

good luck.
0

Featured Post

Technology Partners: We Want Your Opinion!

We value your feedback.

Take our survey and automatically be enter to win anyone of the following:
Yeti Cooler, Amazon eGift Card, and Movie eGift Card!

Question has a verified solution.

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

Update (December 2011): Since this article was published, the things have changed for good for Android native developers. The Sequoyah Project (http://www.eclipse.org/sequoyah/) automates most of the tasks discussed in this article. You can even fin…
This article shows you how to optimize memory allocations in C++ using placement new. Applicable especially to usecases dealing with creation of large number of objects. A brief on problem: Lets take example problem for simplicity: - I have a G…
The viewer will learn how to use and create keystrokes in Netbeans IDE 8.0 for Windows.
The viewer will learn how to user default arguments when defining functions. This method of defining functions will be contrasted with the non-default-argument of defining functions.

710 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