Zombie command window after debugging VS2008
-
Hi, Strange issue a colleague and I have been having intermittently since last week. Basically, after debugging a C++ console app in Visual Studio 2008 (usually via F7 to rebuild after making a code change), sometimes the command window stays open and cannot be closed by any method we can think of. Running the application in debug again opens a new command window. Windows will not reboot once one of these zombie window is there, the machine has to be powered-off. This has occurred with 3 different applications so far. Process Explorer tells me "Unable to find the window's owning process in the current process list" when I "target" the window with "Find window's process". I found this thread after a bit of Googling: http://social.msdn.microsoft.com/Forums/en-US/vsdebug/thread/e6d4a4f5-7002-401a-90e1-6174d7f9e3ca[^] Anyone else experiencing similar? Tempting to blame last week's Patch Tuesday...
-
Hi, Strange issue a colleague and I have been having intermittently since last week. Basically, after debugging a C++ console app in Visual Studio 2008 (usually via F7 to rebuild after making a code change), sometimes the command window stays open and cannot be closed by any method we can think of. Running the application in debug again opens a new command window. Windows will not reboot once one of these zombie window is there, the machine has to be powered-off. This has occurred with 3 different applications so far. Process Explorer tells me "Unable to find the window's owning process in the current process list" when I "target" the window with "Find window's process". I found this thread after a bit of Googling: http://social.msdn.microsoft.com/Forums/en-US/vsdebug/thread/e6d4a4f5-7002-401a-90e1-6174d7f9e3ca[^] Anyone else experiencing similar? Tempting to blame last week's Patch Tuesday...
-
Hi, Strange issue a colleague and I have been having intermittently since last week. Basically, after debugging a C++ console app in Visual Studio 2008 (usually via F7 to rebuild after making a code change), sometimes the command window stays open and cannot be closed by any method we can think of. Running the application in debug again opens a new command window. Windows will not reboot once one of these zombie window is there, the machine has to be powered-off. This has occurred with 3 different applications so far. Process Explorer tells me "Unable to find the window's owning process in the current process list" when I "target" the window with "Find window's process". I found this thread after a bit of Googling: http://social.msdn.microsoft.com/Forums/en-US/vsdebug/thread/e6d4a4f5-7002-401a-90e1-6174d7f9e3ca[^] Anyone else experiencing similar? Tempting to blame last week's Patch Tuesday...
-
Hi, Strange issue a colleague and I have been having intermittently since last week. Basically, after debugging a C++ console app in Visual Studio 2008 (usually via F7 to rebuild after making a code change), sometimes the command window stays open and cannot be closed by any method we can think of. Running the application in debug again opens a new command window. Windows will not reboot once one of these zombie window is there, the machine has to be powered-off. This has occurred with 3 different applications so far. Process Explorer tells me "Unable to find the window's owning process in the current process list" when I "target" the window with "Find window's process". I found this thread after a bit of Googling: http://social.msdn.microsoft.com/Forums/en-US/vsdebug/thread/e6d4a4f5-7002-401a-90e1-6174d7f9e3ca[^] Anyone else experiencing similar? Tempting to blame last week's Patch Tuesday...
-
I'm having the same problem and I believe it started to happen after MS Windows update last week or so.
The solution seems to be to uninstall KB978037. If anyone knows how to escalate this issue with MS, please let me know. We have a minimal code sample that allows the zombie window problem to be readily reproduced. See the MSDN forum link in my original post for more info.
-
The solution seems to be to uninstall KB978037. If anyone knows how to escalate this issue with MS, please let me know. We have a minimal code sample that allows the zombie window problem to be readily reproduced. See the MSDN forum link in my original post for more info.
-
Hi, Strange issue a colleague and I have been having intermittently since last week. Basically, after debugging a C++ console app in Visual Studio 2008 (usually via F7 to rebuild after making a code change), sometimes the command window stays open and cannot be closed by any method we can think of. Running the application in debug again opens a new command window. Windows will not reboot once one of these zombie window is there, the machine has to be powered-off. This has occurred with 3 different applications so far. Process Explorer tells me "Unable to find the window's owning process in the current process list" when I "target" the window with "Find window's process". I found this thread after a bit of Googling: http://social.msdn.microsoft.com/Forums/en-US/vsdebug/thread/e6d4a4f5-7002-401a-90e1-6174d7f9e3ca[^] Anyone else experiencing similar? Tempting to blame last week's Patch Tuesday...
-
Hi, Strange issue a colleague and I have been having intermittently since last week. Basically, after debugging a C++ console app in Visual Studio 2008 (usually via F7 to rebuild after making a code change), sometimes the command window stays open and cannot be closed by any method we can think of. Running the application in debug again opens a new command window. Windows will not reboot once one of these zombie window is there, the machine has to be powered-off. This has occurred with 3 different applications so far. Process Explorer tells me "Unable to find the window's owning process in the current process list" when I "target" the window with "Find window's process". I found this thread after a bit of Googling: http://social.msdn.microsoft.com/Forums/en-US/vsdebug/thread/e6d4a4f5-7002-401a-90e1-6174d7f9e3ca[^] Anyone else experiencing similar? Tempting to blame last week's Patch Tuesday...
I've been having this issue as well for the last two months or so, and found it very annoying (I work remotely and sometimes need to reboot the machine - the presence of orphan windows makes it impossible). Guess I'm not adding anything useful to this discussion, but maybe if enough voices of protest are raised, Redmond would do something about it.