Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    text
    copied!<p>I think I may finally at least know the cause, though not the reason why. When the problem started occurring again, I noticed a ton of "conhost.exe" processes orphaned. I would close Visual Studio and they would remain open. Ending task on each of them has finally, reliably solved the problem. [hopefully]</p> <p>(Just note, conhost.exe isn't a Visual Studio process though Visual Studio uses it. Thus, other users out there may have other applications out there that run conhost.exe. I know my machine doesn't which is why I can safely end task all of them but YMMV.)</p> <p>As to why this happens? It seems to occur when I open more than one project at once, which I tend to do often, even though I only build and debug one of them at any time.</p> <hr> <p>Edit #1 - This isn't a "silver bullet" unfortunately. It doesn't always work for me. Typically, when things get slow, I just close all of my Visual Studio sessions, then go into the task manager and end any instance of it, conhost.exe, iisexpress.exe Microsoft.VisualStudio.Web.Host.exe and MSBuild.exe I can find.</p> <p>Typically, after that, when I restart my project it'll then load quickly. But not always.</p> <p>Really I think the best course of action is probably to not build &amp; debug code off a redirected folder/network share.</p> <hr> <p>Edit #2 - Two years later, and this is <em>still</em> an issue for me in Visual Studio Community 2013, but I did seem to at least find the culprit task: <strong>Explorer.exe</strong>. Yeah, who knew. The moment I end that task, bam, page loads in a single second.</p> <p>If I have a Windows Explorer file browser open to my redirected network drive (which is often since that's where my code is), this problem seems to occur. Closing the window isn't enough, I have to kill the whole Explorer.exe task. I could only guess what it's doing...going nuts with file handles?</p> <p>I can usually use the task manager to start up a new explorer.exe task (I can only take so much alt-tabbing), and Visual Studio will continue to load nice and quick. But if I so much as open Windows Explorer again, it almost always goes back to super-slow-mo.</p> <p>So, if you've got a redirected network share, give it a shot. It sure beats working locally.</p>
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload