Have Geek Brain

Why does Windows Explorer search freeze when I have an unrelated program paused in the debugger

While debugging my program, be it an ASP.NET application or a .NET EXE console, and I have the debugger paused at a breakpoint, I am trying to find the file in Windows Explorer. Either pressing WinKey + F or selecting search from the context menu freezes Windows Explorer - until I resume the program being debugged.

My program has nothing to do with Windows Explorer! In fact, this happens in Visual Studio 2008 with even the simplest console EXE (WriteLine and ReadLine). I cannot reproduce it with this simple EXE in WinDbg, but it does happen with WinDb debugging of ASP.NET application. Why is this happening and how can I fix it? It's annoying as hell, especially when you don't understand what's going on.

This applies to Windows XP x64 Service Pack 2 (SP2) running .NET 3.5 application.

+2


a source to share


1 answer


I remember reading a blog post (long ago) about this. Here's what I think: Why does the Visual Studio debugger sometimes block the entire Windows GUI

Apparently due to some of the common mutexes that were used by text services, there was some deadlock in the GUI.



Hope it helps.

+3


a source






More articles:


All Articles