Visual Studio 2015 not responding

18,814

You could try enabling logging via the /Log command line option of the devenv.exe. See the Microsoft reference. (devenv.exe being the Visual Studio IDE)

Share:
18,814
wonderful world
Author by

wonderful world

Updated on July 25, 2022

Comments

  • wonderful world
    wonderful world almost 2 years

    I have recently installed Windows 10 in my DELL laptop. I see quite often Visual Studio 2015 not responding.

    Is there a log that I can turn on to see what's happening in the Visual Studio while loading a project, to see any add-on delaying the load? Or something like that in the Task Monitor to see which resource is causing the slowness like disk read or memory?

    enter image description here

    enter image description here

    enter image description here

    UPDATE:

    As per IInspectable's comment, I created a dump file from the Task Manager.

    I don't see any thread information in this file. I tried to debug (by clicking debug from the actions menu) after loading the data in VS 2015 again. That takes a while to load the symbols, but at the end I see Source Not Available screen and stop there.

    11/18/2015: Asp.net tools team is working on this performance issue.

    • IInspectable
      IInspectable over 8 years
      Create a minidump, when an application is no longer responding (e.g. by switching to Task Manager's Processes tab, rightclicking the respective process and choosing Create dump file). The dump can then be loaded into a debugger, allowing to inspect the threads. Since the "Not Responding" is caused by GUI threads failing to respond to messages, you already know which threads to concentrate on. Microsoft provides public symbols for all relevant system DLLs, making the call stacks actually useful.
  • David Vitoux
    David Vitoux about 8 years
    "Is there a log that I can turn on to see what's happening in the Visual Studio while loading a project, to see any add-on delaying the load?"
  • jpaugh
    jpaugh about 7 years
    David, Welcome to Stack Overflow! Short answers are unfortunately likely to be mistaken for bad answers, due to the process in place. Including relevant information from your link would have avoided this trap, and perhaps make for an even better answer.