Why the big hangup?

[WSinc]

I noticed something NEW that has come up - -

When I am debugging a program and close the window, it hangs for several minutes.

It did not use to do that. The breakpoint occurred after a few seconds previously.

It's supposed to generate a breakpoint, but I don't see why it should make the debugger

inaccessable for such a long period of time.

As long as it is not trying write into the window,

why would that cause a breakpoint anyway?

One can avoid this by issuing a Ctl-C first, or saying "stop debugging" rather than just closing the window -

But I still don't see why this problem would occur.

[Udit_P_Intel]

Is this a new version of the compiler? Or Visual Studio?

[WSinc]

The problem is with Visual Studio, as far as I can tell. I have VS 2010.

[WSinc]

I downloaded the newest fortran, I think it came with a newer VS. same problem occurs.

[Steven_L_Intel1]

I haven't experienced this myself and don't recall seeing others reporting it. I am not exactly sure I understand your description, however. When you say you "close the window", which window are you closing? Is the program still running in the debugger? Is this a console application, QuickWin, Windows API windowing - which? Please elaborate on the breakpoint issue.

[WSinc]

This happens when the program is still running and I close the console window. it's a console application I am debugging. what happens is that it takes a long time to generate the breakpoint, then after it does, the VS 2010 goes to "la-la land" for several minutes. It says "Visual Studio not responding" when I try to do anything after that. Then after 5-6 minutes, it snaps out of it. I will try turning off the anti-spyware to see if that might be affecting this issue.

[Steven_L_Intel1]

What breakpoint are you referring to? Usually closing a console application window causes a forced exit of the application.

[WSinc]

BYW, I sometimes get a nonsensical message ehwn I try to mofy the source code when the program is still running. It says "refernece item not referenced." I never saw that before. What does that mean?

[WSinc]

BYW, I sometimes get a nonsensical message ehwn I try to mofy the source code when the program is still running. It says "refernece item not referenced." I never saw that before. What does that mean?

[WSinc]

It DOES force a breakpoint when I close the window, but why would it hang everything up for such a long time? It didn't use to be a problem. I testeds it with this: i=0 do i=i+1 print *,i enddo end

[Steven_L_Intel1]

The next time this message occurs, please take a screenshot of it and attach it to a reply here. I don't recognize the message. I just tried the sample program you showed, and when I closed the console window I instantly got the breakpoint related to the error: forrtl: error (200): program aborting due to window-CLOSE event Is the real program where you see this behavior CPU-bound like this one was? It could be something outside Visual Studio is interfering with the process.