Your app has entered a break state, but there is no code to show because all threads were executing external code (typically system or framework code)

Question

Visual Studio 2017 breaks in debug mode and displays the message:

Your app has entered a break state, but there is no code to show because all threads were executing external code (typically system or framework code).

The message is in the Break Mode Window.

What to do?

My guess is, this is unrelated. I have 'enable just my code' on and also 'warn if no user code on launch' on. — Gerard, Oct 21 '17 at 16:06
I disabled 'Just my code' debug property and then got a meaningful error message which I could solve. In my case the error was a .png image not found, as I hadn't set the resource properties correctly, which gave rise to the break state. — Greg Trevellick, Jan 29 '18 at 22:22
I get the same issue every time I am in a debug mode and stay on a breakpoint for too long (I need to stay for long to research the state of the application). Then I click to Continue and get the error. I suspect that there is a setting somewhere which configures for how long I am allowed to suspend the thread for a debug purpose. Does anyone know where can I configure more time for the debug pause? — hellouworld, Dec 05 '19 at 09:20

score 70 · Answer 1 · answered Dec 20 '17 at 08:06

70

Click on "Continue execution"

Then you will have the stacktrace in the output tab

answered Dec 20 '17 at 08:06

Led Machine

7,122
3
47
49

11

Also check that you built your project in Debug mode and not Release mode. – Brad Aug 21 '18 at 16:44
1

This is helpful becuase the root of the problem from my experiance is always some unhandled exception in some an async thread.... – axa Nov 16 '19 at 23:25

Mohammad Atiour Islam · Answer 2 · 2017-11-13T09:34:21.427

20

First check all your common exception setting run time in your visual studio so that you can get the actual error.

During loading you application check that is their any method which is throw new NotImplementedException();

In my case i use INavigationAware which was throw new NotImplementedException(); i just remove those

In you all project update all from nuget.
Clean and rebuild you project.

edited Nov 13 '17 at 09:34

answered Nov 07 '17 at 20:33

Mohammad Atiour Islam

5,380
3
43
48

In my case, there was a problem with the Microsoft.SharePoint NuGet package I downloaded. This resolves my issue. – morethanyell Jan 30 '18 at 17:58

score 6 · Answer 3 · answered Nov 13 '17 at 09:51

6

In my case I just need to restore the list of exception settings to the default settings.

answered Nov 13 '17 at 09:51

devowiec

708
6
16

This worked perfectly for me when VS was starting Navisworks Manage after build with my dll. It got rid of five of these external code breaks. – Cameron Forward Aug 26 '18 at 23:31

score 6 · Answer 4 · answered Feb 11 '21 at 15:42

I hit this earlier today with a C++ console application. Disabling "just my code" and selecting the Microsoft symbol server fixed this issue.

Tools → Options → Debugging → General → Untick "Enable Just My Code"

Tools → Options → Debugging → Symbols → Tick "Microsoft Symbol Servers"

score 4 · Answer 5 · answered May 23 '18 at 18:21

4

I got this situation when my "Platform Target" in my Project Properties was set to "Any CPU" and "Prefer 32-bit" was selected.

I switched Platform Target to "x64" since I am using 64-bit assemblies and then I could run/debug normally.

answered May 23 '18 at 18:21

Kevin UI

187
6
14

1

i has the issue and the cause was incompatible Platform Targets for projects within the solution. The compatibility issue is discussed in the 'Understanding the Behaviour of 32-bit, 64-bit and Any CPU compiled PE Files' section of https://www.codeproject.com/Articles/1160645/Dealing-with-bit-bit-and-Any-CPU-Compilation-Optio?display=Print . – Ron Jan 31 '19 at 01:03

score 3 · Answer 6 · answered Apr 20 '18 at 08:29

This solution is for people who get this error in WPF application. I got this error when i moved mainwindow.xaml to view folder and forgot to update in App.Xaml. after updating as StartupUri="View/MainWindow.xaml" the main window loaded without warning.

score 3 · Answer 7 · answered Mar 12 '19 at 16:36

3

For me, I received the error when my console application was set in Release Mode. Switching to Debug mode fixed the issue.

answered Mar 12 '19 at 16:36

Eric

7,930
17
96
128

score 1 · Answer 8 · answered Oct 09 '18 at 06:25

1

Check for any case of circular dependency while injecting dependencies.

answered Oct 09 '18 at 06:25

Honey Dev P

27
1

1

From Review: This post does not seem to provide a [quality answer](https://stackoverflow.com/help/how-to-answer) to the question. Please either edit your answer and improve it, or just post it as a comment to the question. – sɐunıɔןɐqɐp Oct 09 '18 at 06:45
See https://stackoverflow.com/questions/25669677/unity-resolving-cyclic-dependency – kristianp Dec 17 '18 at 05:59
I also get an issue like this by the circular dependency. – Trung Dec 22 '20 at 09:27
Vote up from me, this was exactly my problem – Richard May 23 '21 at 15:59

score 1 · Answer 9 · edited Jun 12 '20 at 00:30

1

This type of issue please check property and Accessories. We should return correct field and check value field.

Example:

private string NameField;
public string Name
{
  get
  {
  return NameField;
  }
  set
  {
  nameField=value;
  }
}

edited Jun 12 '20 at 00:30

Pang

9,564
146
81
122

answered Dec 04 '18 at 07:33

Rajenthiran T

77
1
6

score 1 · Answer 10 · answered Sep 30 '20 at 19:41

1

Just had a similar issue in VS2019, I ended up needing to rebuild all in order to resolve the issue despite having manually built many times.

answered Sep 30 '20 at 19:41

jeff curley

11
3

I had to clean my solution first then rebuild and then restart IIS server as I was debugging an ASP.NET web API hosted in IIS. – RBT Sep 22 '21 at 09:33

score 0 · Answer 11 · answered Oct 08 '17 at 18:48

0

First drag the Break Mode Window to the Call Stack Window to get an overview again.

Then, check whether the Solution Explorer Window is in source mode. The 4th button from the left has a drop-down. Make sure the *.sln, i.e. classic solution mode is selected.

I didn't know this and was surprised to find that in "source mode", i.e. the other possibility, the above mentioned message is displayed.

answered Oct 08 '17 at 18:48

Gerard

13,023
14
72
125

hi, can you explain about `check whether the Solution Explorer Window is in source mode` ? because I have only 'Folder View' in this dropdown... – vladimir Oct 31 '17 at 17:08
This surprises me, I now also see only a Folder View .. There been VS updates, I now have 15.4.1, I assume that is the reason but I am not sure. – Gerard Nov 01 '17 at 17:43
What is this in aid of exactly? – Ortund Jul 31 '18 at 10:48

score 0 · Answer 12 · answered Jan 10 '18 at 17:27

0

I got this when I accidentally set the startup project to a class library instead of the end project (in this case, a WPF application).

answered Jan 10 '18 at 17:27

Zev Spitz

13,950
6
64
136

Ramanujam Allam · Answer 13 · 2018-04-19T11:38:36.183

0

Observed same error and resolved it by:

Removing duplicate configs from section
Removing extra/unused characters (by mistakenly entered)

edited Apr 19 '18 at 11:38

answered Apr 19 '18 at 06:51

Ramanujam Allam

1,300
12
11

score 0 · Answer 14 · answered Jul 31 '18 at 22:38

0

This occurred for me when I placed the connectionStrings config item in the wrong spot in app.config.

answered Jul 31 '18 at 22:38

Mike S.

402
1
3
13

score 0 · Answer 15 · answered Aug 27 '18 at 15:52

0

check your Ip address (it must be the same as the listening adress if you'r not using the loopbach address)

answered Aug 27 '18 at 15:52

Fatma Labidi

19
2

score 0 · Answer 16 · edited Jun 20 '20 at 09:12

Error: IOException Cannot locate resource

Most of the time this error occur when using visual studio form applications.

To solve this error you can go to your App.xaml file and edit SratupUri to your current xaml form name.

<Application x:Class="AppName.App"
             xmlns="http://schemas.microsoft.com/winfx/2006/xaml/presentation"
             xmlns:x="http://schemas.microsoft.com/winfx/2006/xaml"
             StartupUri="MainWindow.xaml">
    <Application.Resources>
    </Application.Resources>
</Application>

score 0 · Answer 17 · edited Jun 12 '20 at 00:31

You can also experience this issue if you've altered the build process with something like this to remove the PDB files. Typically I recommend if you want to remove the PDB files make the configuration specific to the "Release" configuration:

<Target Name="RemoveTranslationsAfterBuild" AfterTargets="AfterBuild" Condition=" '$(Configuration)|$(Platform)' == 'Release|AnyCPU' ">
    <RemoveDir Directories="@(FluentValidationExcludedCultures->'$(OutputPath)%(Filename)')" />

    <ItemGroup>
        <PDBFilesToDelete Include="$(TargetDir)\*.pdb"/>
    </ItemGroup>
    <Delete Files="@(PDBFilesToDelete)" />
</Target>

Then Follow @Eric's recommendations when debugging run the build under the "Debug" configuration.

score 0 · Answer 18 · answered Aug 28 '19 at 04:21

0

I got similar issue, after spending 2 days we figured out it was due to my application was terminated from out side at the same time I was debugging.

answered Aug 28 '19 at 04:21

Imad

7,126
12
55
112

score 0 · Answer 19 · answered Jul 15 '20 at 14:00

Had the same problem, this was due to having the build set to release build. Then when asked if I would like to debug, I accidentally clicked ignore always.

I changed it to debug mode in the properties settings but the error was still there.

You will also need to change this in the configuration manager from Build/configuration manager and set Configuration to Debug as well.

score 0 · Answer 20 · edited Oct 30 '20 at 05:25

0

Same here. Reinstalling VS 2019 solved it.

edited Oct 30 '20 at 05:25

Bhargav Rao

50,140
28
121
140

answered Oct 29 '20 at 21:29

ADBF

93
1
15

score 0 · Answer 21 · answered Nov 07 '21 at 08:05

Even though this is an older post, I thought the solution to my problem could help others looking for an answer to this problem.

Using the above suggestion from Led Machine - to see the stack trace, I found the following top lines.

Exception Info: System.NullReferenceException at System.Web.ThreadContext.AssociateWithCurrentThread(Boolean) at System.Web.HttpApplication.OnThreadEnterPrivate(Boolean) at System.Web.LegacyAspNetSynchronizationContext.CallCallbackPossiblyUnderLock(System.Threading.SendOrPostCallback, System.Object)

Googling this stack trace, sent me to this page: https://techcommunity.microsoft.com/t5/iis-support-blog/crash-at-system-web-legacyaspnetsynchronizationcontext/ba-p/1536553

Apparently, the problem was related to my application being configured to use Legacy ASP.NET Synchronization Context, and in certain parts of the code, I was using some new features, such as Tasks. The old (Legacy) context cannot handle some asynchronous calls properly and this leads to the crash as observed in the above.

The fix is to insert the following line in your web.config:

<appSettings>
<add key="aspnet:UseTaskFriendlySynchronizationContext" value="true" />
</appSettings>

score -1 · Answer 22 · answered Apr 09 '19 at 01:05

-1

I had a similar issue when debugging a VSTO Excel add-in. After trying everything, I resolved the issue by disabling a realtime protection module on my antivirus software.

answered Apr 09 '19 at 01:05

Blobby

1

Can you elaborate on how to disable that? – JJJ Apr 09 '19 at 01:15
1

:D I'm so lost that I'm actually going to try this :D – DurkoMatko Sep 22 '20 at 13:57

Your app has entered a break state, but there is no code to show because all threads were executing external code (typically system or framework code)

22 Answers22

Error: IOException Cannot locate resource

Linked