Why are debug symbols called debug symbols

Visual Studio loading icons

I've been working on a ColdFusion project for a while now, and Visual Studio was acting strange, at least for me.

When I started debugging, I found that the project was built, the deployment started, the deployment stopped, and icons for my project were loading.

But it was very slow and I don't know why it started this step. What can i have done

Is this step required to load the symbol? How can I turn it off?

No location was added for the symbol file (.pdb) in the Tools -> Options -> Debug -> Symbols dialog box. In my project's debug directory, I pointed to the box below and checked the "Only search directory above if symbols ... are" check box. How should I set up this dialog to disable the loading of symbols?

I've looked in the module window to see what symbols are loaded, but it doesn't tell me anything. What is the problem?


Another reason for slow loading is if you unchecked "Enable my code only" in the debugging options. To enable this go to:

Make sure this is checked.

Configure in Tools, Options, Debugging, Symbols.

You can watch the output window (view, output) to see what it does normally. If it is very slow, it likely means that it is hitting a symbol server, probably Microsoft's, to download missing symbols. This requires three HTTP hits for each file, which cannot be found on every startup. This is sometimes shown in the status bar below or e.g. B. displayed in Fiddler. You can see which modules have symbols loaded in Debug, Windows, Modules while you are debugging.

Icons mean you can get useful information about batch tracking in third party assemblies and systems. You definitely need them for your own code, but I think these will load anyway. It is best to deactivate all non-local symbol sources in this menu. If you are loading a large number of symbols for system assemblies that you do not need to debug, you can temporarily disable loading of them to speed up debugging. but they are often useful to have charged.

Just had this problem.

I fixed it by navigating to:

Extras -> Options -> Debug -> Symbols

Then disable all non-local sources for Icon file (.pdb) locations

e.g. Microsoft Icon Server and msdl.microsoft.com/download/symbols

I had a similar problem. In my case, I had _NT_SYMBOL_PATH set to download from Microsoft servers for use in WinDbg, and it looks like Visual Studio is using this without ignoring it. Removing this environment variable fixed my problem.

You can try the following answer to debug / load Visual Studio very slowly:

  1. Go to Tools -> Options -> Debugging -> General

  2. Activate the check mark next to "Only activate my code".

  3. Go to Tools -> Options -> Debug -> Symbols

  4. Click the "..." button and create / select a new folder somewhere on your local computer to save cached icons. I called my "Icon Caching" and added it to "Documents -> Visual Studio 2012".

  5. Click "Get All Icons" and wait for the icons to download from Microsoft's servers. This can take a while. Note that the Load All Symbols button is only available when debugging.

  6. Uncheck the box next to Microsoft Symbol Server to prevent Visual Studio from polling the Microsoft servers remotely.

  7. Click OK ".

Also try clearing all breakpoints (Debug> Clear All Breakpoints).

See also : Visual Studio 2015 RC1 hangs when loading symbols in debug mode

To me they seem to be breakpoints as stated in the accepted answer. However, I found two workarounds where not all breakpoints were cleared:

  • Restarting Visual Studio seemed to temporarily fix the problem.
  • If you click the "X" button to close Visual Studio while debugging, it says "Do you want to quit debugging?" Message box for surfacing; While this message box is open, the icons will load at normal speed. Once all symbols are loaded, you can click "No" to cancel closing.

I just ran into this problem. Deleting breakpoints didn't work, or at least didn't work on its own. After that failed I went to Tools> Options> Debugging> Symbols and "Empty Symbol Cache".

and then the solution cleaned and rebuilt.

Seems to work properly now. So if you try all of the other things listed and it still doesn't make a difference, this additional information can help ...

In my case, Visual Studio was looking for third-party PDBs in paths pointing to an optical drive on my computer. Without a CD in the system tray, Windows took about 30 minutes to fail, which in turn slowed Visual Studio down when it tried to load the PDBs from that location. For more details, see my full answer here: https://stackoverflow.com/a/17457581/85196

I had the same problem and even after turning off the icon loading, the module loading in Visual Studio was terribly slow.

The solution was to disable the antivirus software (in my case NOD32) or better yet and add exceptions to ignore the paths your process loads assemblies from (in my case the GAC folder and the temporary ASP folder .NET) Files).

My 2 cents,

I had a similar problem while trying to get a (Visual Studio 2013) diagnostic report in x64 (CPU sampling) release mode and while the icons for the required DLL files were loading, the icons for my executable failed to load.

I didn't change anything in the Icons menu, instead I made some changes in the property pages of the thread of my executable in Solution Explorer, namely

Enable Configuration Properties / General / Managed Incremental Build to YES

Configuration Properties / Debugging / Merge Environment to NO

Configuration Properties / C / C ++ / Enable Browse Information to YES (/ FR)

Activate configuration properties / Linker / Incremental link with YES (/ INCREMENTAL)

EDIT: This last one does the trick


Configuration Properties / Linker / Debugging / Generate debug information on Yes (/ DEBUG)


After that it worked and the icons loaded well. I'm sure one or more of the above did the trick for me (although I'm not sure which one) and I just want to let others know and try this.


Try right-clicking one of the breakpoints, then choose Location. Then select the "Allow the source code to be different from the original version" check box.

Visual Studio 2017 Ease Options debug icon, assuming you haven't gone crazy with option customization:

  1. At
    one. Activate the option "Microsoft Symbol Server".
    B. Click Clear Icon Cache.
    C. Set your icon cache to an easy-to-find dot like or
  2. After running Debug again, let all symbols load once, from start to finish, or as far as possible.

1A and 2 are the most important steps. 1B and 1C are just helpful changes to keep track of your symbols.

After your app has loaded all of the symbols at least once and has not stopped debugging prematurely, these symbols should load quickly the next time you debug.

I have found that when I abort a debug run I have to reload these symbols as I suspect that they will be "cleaned up" if they are reintroduced and suddenly aborted. I understand the main reasons for this type of flow, but in this case it seems ill-conceived.

By disabling "Enable JavaScript debugging for ASP.NET (Chrome and IE)" under Tools-> Options-> Debugging-> General, my case was resolved because the VS2017 debugger could not be started with preset breakpoints.

The only thing that worked for me was changing the code type.

In the window Attach to process i choose attach to changed , to debug the Code type to be determined automatically. Then my breakpoints were reached.

I only had before native Code selected.

I had a similar problem where Visual Studio kept loading the icon and getting stuck.

It turns out that I put some "command line arguments" in the debug options and one of the parameters is invalid (I'm supposed to pass some values).

After removing the extra parameter, it works again.

We use cookies and other tracking technologies to improve your browsing experience on our website, to show you personalized content and targeted ads, to analyze our website traffic, and to understand where our visitors are coming from.

By continuing, you consent to our use of cookies and other tracking technologies and affirm you're at least 16 years old or have consent from a parent or guardian.

You can read details in our Cookie policy and Privacy policy.