Search code examples
c++visual-studiodebuggingvisual-studio-2015crash

Visual Studio 2015 crashes when starting debugger

When compiling my C++ project or running it, everything is fine.
But when starting my project with the debugger, Visual Studio 2015 crashes.
I tried this, I have found two errors: 

<entry>
  <record>484</record>
  <time>2017/02/14 14:09:32.187</time>
  <type>Error</type>
  <source>Color Theme Service</source>
  <description>The color &apos;Popup&apos; in category &apos;de7b1121-99a4-4708-aedf-15f40c9b332f&apos; does not exist.</description>
</entry>

and

<entry>
<record>558</record>
  <time>2017/02/14 14:10:08.617</time>
  <type>Error</type>
  <source>VisualStudio</source>
  <description>Loading UI library</description>
  <guid>{8C0C630B-37F1-11E3-8259-6C3BE516EAD0}</guid>
  <hr>800a006f</hr>
</entry>

I don't know what to do to make VS's debugger work.

Edit: I use the dark theme if this can help...

Solution

  • One issue is that whether all projects have the same issue or just the specific one.

    (1) Collect the crashed dump file and debugging it is also a good suggestion for the crashed issue.

    (2) I also provide some suggestions which could narrow down this issue.

    • Please uncheck symbols server under Tools -> Options -> Debugging -> Symbols.
    • Uncheck "Edit and continue", "Load dll exports (native only)" and "enable just my code(managed only)". Debug it again.
    • Disable the IntelliTrace under TOOLS->Options->IntelliTrace, and "Use Native Compatibility Mode" under TOOLS->Option->Debugging->General or mix mode/native debugging project property(right click project->Debugging). Test it again.

    I met the crashed issue before which was related to certain settings, so if possible, you could test it in your side.

    But if all projects have the same issue, I suggest you repair your VS, or install the latest update package for your VS, and then debug it again.

    If just one specific project has this issue, we would think about the project itself.

    Update:

    As our discussion, I found that you have reported this issue here:

    https://connect.microsoft.com/VisualStudio/Feedback/Details/3123487

    I will help you vote it and add my comment there. If I get any latest information from the report team, I will update it here.