The application is in break mode - Unable to determine cause
I'm experiencing that the IDE breaks sometimes when my application terminates.
When this occurs, the call stack is empty, and the thread list shows some threads which don't reveal any information to me.
When I choose "Debugger"-"Step into", the IDE quits / terminally seemingly normally, so I don't see how I could further investigate what causes the breaking.
Clicking "Check for running Tasks" doesn't display any tasks.
Clicking "Continue executing" quits debugging seemingly normally.
Clicking "Show diagnostic tools" shows the event "Stop at Execution: Stopped at Execution", which doesn't tell me any more.
A screenshot is attached.
How can I investigate what's causing this break?
Edit:
I've tried what one forum member suggested, but that wouldn't result in anything that would help me, I think. This is a screenshot:
vb.net debugging ide visual-studio-2017
asked Sep 7 '17 at 18:31
tmightytmighty
2,2171058128
add a comment |
I'm experiencing that the IDE breaks sometimes when my application terminates.
When this occurs, the call stack is empty, and the thread list shows some threads which don't reveal any information to me.
When I choose "Debugger"-"Step into", the IDE quits / terminally seemingly normally, so I don't see how I could further investigate what causes the breaking.
Clicking "Check for running Tasks" doesn't display any tasks.
Clicking "Continue executing" quits debugging seemingly normally.
Clicking "Show diagnostic tools" shows the event "Stop at Execution: Stopped at Execution", which doesn't tell me any more.
A screenshot is attached.
How can I investigate what's causing this break?
Edit:
I've tried what one forum member suggested, but that wouldn't result in anything that would help me, I think. This is a screenshot:
vb.net debugging ide visual-studio-2017
asked Sep 7 '17 at 18:31
tmightytmighty
2,2171058128
Please view the task manager, and check that whether certain processes which were related to the debugger tool/this project were not closed, you could close them, and then view the debugging result, or just restart your machine, re-open the project, debug it again. Make sure and run a "clean" under build, or you could get certain compiled error or exception in your side.
– Jack Zhai-MSFT
Sep 8 '17 at 9:39
@JackZhai-MSFT Please explain more in detail what I should do.
– tmighty
Sep 12 '17 at 22:26
1
It looks pretty unhealthy. The finalizer thread is no longer running but there are still three threads running managed code. Not good. Crystal ball says that you noticed the two second timeout at program termination, a hint that the finalizer thread was deadlocked. You have a good reason to contact your component vendor's support, Essential Objects is in the business of supplying risky code that is likely to cause finalizer thread deadlocks.
– Hans Passant
Sep 13 '17 at 8:35
When I faced a similar issue, my problem turned out to be a forgotten break point on a threaded method. Disabling all break points prior to running your app could prove or disprove this theory. Can't remember if my break point was in a referenced project, but it was definitely related.
– blaze_125
Sep 19 '17 at 21:01
add a comment |
I'm experiencing that the IDE breaks sometimes when my application terminates.
When this occurs, the call stack is empty, and the thread list shows some threads which don't reveal any information to me.
When I choose "Debugger"-"Step into", the IDE quits / terminally seemingly normally, so I don't see how I could further investigate what causes the breaking.
Clicking "Check for running Tasks" doesn't display any tasks.
Clicking "Continue executing" quits debugging seemingly normally.
Clicking "Show diagnostic tools" shows the event "Stop at Execution: Stopped at Execution", which doesn't tell me any more.
A screenshot is attached.
How can I investigate what's causing this break?
Edit:
I've tried what one forum member suggested, but that wouldn't result in anything that would help me, I think. This is a screenshot:
vb.net debugging ide visual-studio-2017
asked Sep 7 '17 at 18:31
tmightytmighty
2,2171058128
I'm experiencing that the IDE breaks sometimes when my application terminates.
When this occurs, the call stack is empty, and the thread list shows some threads which don't reveal any information to me.
When I choose "Debugger"-"Step into", the IDE quits / terminally seemingly normally, so I don't see how I could further investigate what causes the breaking.
Clicking "Check for running Tasks" doesn't display any tasks.
Clicking "Continue executing" quits debugging seemingly normally.
Clicking "Show diagnostic tools" shows the event "Stop at Execution: Stopped at Execution", which doesn't tell me any more.
A screenshot is attached.
How can I investigate what's causing this break?
Edit:
I've tried what one forum member suggested, but that wouldn't result in anything that would help me, I think. This is a screenshot:
vb.net debugging ide visual-studio-2017
vb.net debugging ide visual-studio-2017
asked Sep 7 '17 at 18:31
tmightytmighty
2,2171058128
asked Sep 7 '17 at 18:31
tmightytmighty
2,2171058128
edited Sep 12 '17 at 12:43
tmighty
asked Sep 7 '17 at 18:31
tmightytmighty
2,2171058128
asked Sep 7 '17 at 18:31
tmightytmighty
2,2171058128
asked Sep 7 '17 at 18:31
tmightytmighty
2,2171058128
2,2171058128
Please view the task manager, and check that whether certain processes which were related to the debugger tool/this project were not closed, you could close them, and then view the debugging result, or just restart your machine, re-open the project, debug it again. Make sure and run a "clean" under build, or you could get certain compiled error or exception in your side.
– Jack Zhai-MSFT
Sep 8 '17 at 9:39
@JackZhai-MSFT Please explain more in detail what I should do.
– tmighty
Sep 12 '17 at 22:26
1
It looks pretty unhealthy. The finalizer thread is no longer running but there are still three threads running managed code. Not good. Crystal ball says that you noticed the two second timeout at program termination, a hint that the finalizer thread was deadlocked. You have a good reason to contact your component vendor's support, Essential Objects is in the business of supplying risky code that is likely to cause finalizer thread deadlocks.
– Hans Passant
Sep 13 '17 at 8:35
When I faced a similar issue, my problem turned out to be a forgotten break point on a threaded method. Disabling all break points prior to running your app could prove or disprove this theory. Can't remember if my break point was in a referenced project, but it was definitely related.
– blaze_125
Sep 19 '17 at 21:01
add a comment |
Please view the task manager, and check that whether certain processes which were related to the debugger tool/this project were not closed, you could close them, and then view the debugging result, or just restart your machine, re-open the project, debug it again. Make sure and run a "clean" under build, or you could get certain compiled error or exception in your side.
– Jack Zhai-MSFT
Sep 8 '17 at 9:39
@JackZhai-MSFT Please explain more in detail what I should do.
– tmighty
Sep 12 '17 at 22:26
1
It looks pretty unhealthy. The finalizer thread is no longer running but there are still three threads running managed code. Not good. Crystal ball says that you noticed the two second timeout at program termination, a hint that the finalizer thread was deadlocked. You have a good reason to contact your component vendor's support, Essential Objects is in the business of supplying risky code that is likely to cause finalizer thread deadlocks.
– Hans Passant
Sep 13 '17 at 8:35
When I faced a similar issue, my problem turned out to be a forgotten break point on a threaded method. Disabling all break points prior to running your app could prove or disprove this theory. Can't remember if my break point was in a referenced project, but it was definitely related.
– blaze_125
Sep 19 '17 at 21:01
Please view the task manager, and check that whether certain processes which were related to the debugger tool/this project were not closed, you could close them, and then view the debugging result, or just restart your machine, re-open the project, debug it again. Make sure and run a "clean" under build, or you could get certain compiled error or exception in your side.
– Jack Zhai-MSFT
Sep 8 '17 at 9:39
Please view the task manager, and check that whether certain processes which were related to the debugger tool/this project were not closed, you could close them, and then view the debugging result, or just restart your machine, re-open the project, debug it again. Make sure and run a "clean" under build, or you could get certain compiled error or exception in your side.
– Jack Zhai-MSFT
Sep 8 '17 at 9:39
@JackZhai-MSFT Please explain more in detail what I should do.
– tmighty
Sep 12 '17 at 22:26
@JackZhai-MSFT Please explain more in detail what I should do.
– tmighty
Sep 12 '17 at 22:26
1
1
It looks pretty unhealthy. The finalizer thread is no longer running but there are still three threads running managed code. Not good. Crystal ball says that you noticed the two second timeout at program termination, a hint that the finalizer thread was deadlocked. You have a good reason to contact your component vendor's support, Essential Objects is in the business of supplying risky code that is likely to cause finalizer thread deadlocks.
– Hans Passant
Sep 13 '17 at 8:35
It looks pretty unhealthy. The finalizer thread is no longer running but there are still three threads running managed code. Not good. Crystal ball says that you noticed the two second timeout at program termination, a hint that the finalizer thread was deadlocked. You have a good reason to contact your component vendor's support, Essential Objects is in the business of supplying risky code that is likely to cause finalizer thread deadlocks.
– Hans Passant
Sep 13 '17 at 8:35
When I faced a similar issue, my problem turned out to be a forgotten break point on a threaded method. Disabling all break points prior to running your app could prove or disprove this theory. Can't remember if my break point was in a referenced project, but it was definitely related.
– blaze_125
Sep 19 '17 at 21:01
When I faced a similar issue, my problem turned out to be a forgotten break point on a threaded method. Disabling all break points prior to running your app could prove or disprove this theory. Can't remember if my break point was in a referenced project, but it was definitely related.
– blaze_125
Sep 19 '17 at 21:01
add a comment |
7 Answers
7
active
oldest
votes
In one of my web applications I had the same issue, to find out what was wrong,after searching for similar issues, most suggested changing my debugging options. So in the debugging options, under general, I marked the second option "Break all processes when one process breaks" and nearly at the bottom, "Enable native Edit and Continue"; "Apply changes and Continue".
With this, my app finally stopped where I had the issue (Illegal characters in a string which ajax did not like) and was able to evaluate the values and find out what was wrong, edit the code on the go till it worked.
Here's a screenshot of my debugger options.
Hope you catch your bug:)
Debugger options
answered Sep 13 '17 at 8:07
Alan WardenAlan Warden
1087
I have the same debugger options now, but unfortunately that doesn't help. I just don't get into the spot where the exception happens. I'm unable to find out which COM object causes the problem.
– tmighty
Sep 19 '17 at 22:12
You said it was when you terminate the app, how about putting the process/processes inside one or several Try/catch methods to see if it gets caught in the exceptions?
– Alan Warden
Sep 20 '17 at 9:31
add a comment |
You may not be able to see the code where the exception happens if it's a part of a library or something else not written by you. The following might help:
Debug > Options > General > Uncheck "Enable Just My Code"
answered Mar 6 '18 at 10:08
AlternatexAlternatex
81431739
add a comment |
When you are in the debugger you can navigate to watch window and use pseudovariables to display some information about the root cause. One particularly useful is $exception.
Check document about pseudovariables.
answered Sep 9 '17 at 18:57
Paweł ŁukasikPaweł Łukasik
2,30411322
When the problem occurs, the IDE tells me "Unable to evaluate the expression.". I've updated my post with the screenshot of it.
– tmighty
Sep 11 '17 at 23:30
Is there no info if you click on 'Stop at Exception' on the right hand side of the Visual Studio?
– Paweł Łukasik
Sep 12 '17 at 6:16
No. If I click on it, nothing happens. When I hover over it, the message "An exception was caught by the debugger, and user settings indicate that a break should occur" is displayed. I've edited my posting to show this.
– tmighty
Sep 12 '17 at 12:44
add a comment |
I didn't find any way to actually debug the problem.
I solved the problem the bruteforce way:
I removed all assemblies and COM objects one by one until the error was gone.
In my case, I had a public control with a WithEvents in a module.
It seems that VB.NET didn't like that at all.
From now on, I will put the control and its withevent in a form.
The main problem however remains: Visual Studio doesn't offer any help to isolate the problem easily.
answered Sep 21 '17 at 20:19
tmightytmighty
2,2171058128
add a comment |
This can also occur when a single threaded Winforms application takes more than 60 seconds to complete an action in the main thread.
I solved it in the dirty way, by calling Application.DoEvents() on regular intervals from the main thread, during too long processing. Exceptions that occur between Application.DoEvents calls are handled properly in the IDE.
answered Dec 23 '17 at 3:09
GoodiesGoodies
42828
1
Is this behaviour documented anywhere?
– cbailiss
Nov 25 '18 at 7:35
add a comment |
Go to exception settings and uncheck "Magaged Debugging Assistants"
answered Jun 27 '18 at 1:55
user3578181user3578181
1,3651010
add a comment |
This can occur because some method or constructor is inaccessible (private or internal), put the as public.
The XAML need call the methods to start application
answered Dec 14 '17 at 16:36
impactroimpactro
13114
add a comment |
Your Answer
StackExchange.ifUsing("editor", function () {
StackExchange.using("externalEditor", function () {
StackExchange.using("snippets", function () {
StackExchange.snippets.init();
});
});
}, "code-snippets");
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "1"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f46102963%2fthe-application-is-in-break-mode-unable-to-determine-cause%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
7 Answers
7
active
oldest
votes
7 Answers
7
active
oldest
votes
active
oldest
votes
active
oldest
votes
In one of my web applications I had the same issue, to find out what was wrong,after searching for similar issues, most suggested changing my debugging options. So in the debugging options, under general, I marked the second option "Break all processes when one process breaks" and nearly at the bottom, "Enable native Edit and Continue"; "Apply changes and Continue".
With this, my app finally stopped where I had the issue (Illegal characters in a string which ajax did not like) and was able to evaluate the values and find out what was wrong, edit the code on the go till it worked.
Here's a screenshot of my debugger options.
Hope you catch your bug:)
Debugger options
answered Sep 13 '17 at 8:07
Alan WardenAlan Warden
1087
I have the same debugger options now, but unfortunately that doesn't help. I just don't get into the spot where the exception happens. I'm unable to find out which COM object causes the problem.
– tmighty
Sep 19 '17 at 22:12
You said it was when you terminate the app, how about putting the process/processes inside one or several Try/catch methods to see if it gets caught in the exceptions?
– Alan Warden
Sep 20 '17 at 9:31
add a comment |
In one of my web applications I had the same issue, to find out what was wrong,after searching for similar issues, most suggested changing my debugging options. So in the debugging options, under general, I marked the second option "Break all processes when one process breaks" and nearly at the bottom, "Enable native Edit and Continue"; "Apply changes and Continue".
With this, my app finally stopped where I had the issue (Illegal characters in a string which ajax did not like) and was able to evaluate the values and find out what was wrong, edit the code on the go till it worked.
Here's a screenshot of my debugger options.
Hope you catch your bug:)
Debugger options
answered Sep 13 '17 at 8:07
Alan WardenAlan Warden
1087
I have the same debugger options now, but unfortunately that doesn't help. I just don't get into the spot where the exception happens. I'm unable to find out which COM object causes the problem.
– tmighty
Sep 19 '17 at 22:12
You said it was when you terminate the app, how about putting the process/processes inside one or several Try/catch methods to see if it gets caught in the exceptions?
– Alan Warden
Sep 20 '17 at 9:31
add a comment |
In one of my web applications I had the same issue, to find out what was wrong,after searching for similar issues, most suggested changing my debugging options. So in the debugging options, under general, I marked the second option "Break all processes when one process breaks" and nearly at the bottom, "Enable native Edit and Continue"; "Apply changes and Continue".
With this, my app finally stopped where I had the issue (Illegal characters in a string which ajax did not like) and was able to evaluate the values and find out what was wrong, edit the code on the go till it worked.
Here's a screenshot of my debugger options.
Hope you catch your bug:)
Debugger options
answered Sep 13 '17 at 8:07
Alan WardenAlan Warden
1087
In one of my web applications I had the same issue, to find out what was wrong,after searching for similar issues, most suggested changing my debugging options. So in the debugging options, under general, I marked the second option "Break all processes when one process breaks" and nearly at the bottom, "Enable native Edit and Continue"; "Apply changes and Continue".
With this, my app finally stopped where I had the issue (Illegal characters in a string which ajax did not like) and was able to evaluate the values and find out what was wrong, edit the code on the go till it worked.
Here's a screenshot of my debugger options.
Hope you catch your bug:)
Debugger options
answered Sep 13 '17 at 8:07
Alan WardenAlan Warden
1087
answered Sep 13 '17 at 8:07
Alan WardenAlan Warden
1087
answered Sep 13 '17 at 8:07
Alan WardenAlan Warden
1087
answered Sep 13 '17 at 8:07
Alan WardenAlan Warden
1087
1087
I have the same debugger options now, but unfortunately that doesn't help. I just don't get into the spot where the exception happens. I'm unable to find out which COM object causes the problem.
– tmighty
Sep 19 '17 at 22:12
You said it was when you terminate the app, how about putting the process/processes inside one or several Try/catch methods to see if it gets caught in the exceptions?
– Alan Warden
Sep 20 '17 at 9:31
add a comment |
I have the same debugger options now, but unfortunately that doesn't help. I just don't get into the spot where the exception happens. I'm unable to find out which COM object causes the problem.
– tmighty
Sep 19 '17 at 22:12
You said it was when you terminate the app, how about putting the process/processes inside one or several Try/catch methods to see if it gets caught in the exceptions?
– Alan Warden
Sep 20 '17 at 9:31
I have the same debugger options now, but unfortunately that doesn't help. I just don't get into the spot where the exception happens. I'm unable to find out which COM object causes the problem.
– tmighty
Sep 19 '17 at 22:12
I have the same debugger options now, but unfortunately that doesn't help. I just don't get into the spot where the exception happens. I'm unable to find out which COM object causes the problem.
– tmighty
Sep 19 '17 at 22:12
You said it was when you terminate the app, how about putting the process/processes inside one or several Try/catch methods to see if it gets caught in the exceptions?
– Alan Warden
Sep 20 '17 at 9:31
You said it was when you terminate the app, how about putting the process/processes inside one or several Try/catch methods to see if it gets caught in the exceptions?
– Alan Warden
Sep 20 '17 at 9:31
add a comment |
You may not be able to see the code where the exception happens if it's a part of a library or something else not written by you. The following might help:
Debug > Options > General > Uncheck "Enable Just My Code"
answered Mar 6 '18 at 10:08
AlternatexAlternatex
81431739
add a comment |
You may not be able to see the code where the exception happens if it's a part of a library or something else not written by you. The following might help:
Debug > Options > General > Uncheck "Enable Just My Code"
answered Mar 6 '18 at 10:08
AlternatexAlternatex
81431739
add a comment |
You may not be able to see the code where the exception happens if it's a part of a library or something else not written by you. The following might help:
Debug > Options > General > Uncheck "Enable Just My Code"
answered Mar 6 '18 at 10:08
AlternatexAlternatex
81431739
You may not be able to see the code where the exception happens if it's a part of a library or something else not written by you. The following might help:
Debug > Options > General > Uncheck "Enable Just My Code"
answered Mar 6 '18 at 10:08
AlternatexAlternatex
81431739
answered Mar 6 '18 at 10:08
AlternatexAlternatex
81431739
answered Mar 6 '18 at 10:08
AlternatexAlternatex
81431739
answered Mar 6 '18 at 10:08
AlternatexAlternatex
81431739
81431739
add a comment |
add a comment |
When you are in the debugger you can navigate to watch window and use pseudovariables to display some information about the root cause. One particularly useful is $exception.
Check document about pseudovariables.
answered Sep 9 '17 at 18:57
Paweł ŁukasikPaweł Łukasik
2,30411322
When the problem occurs, the IDE tells me "Unable to evaluate the expression.". I've updated my post with the screenshot of it.
– tmighty
Sep 11 '17 at 23:30
Is there no info if you click on 'Stop at Exception' on the right hand side of the Visual Studio?
– Paweł Łukasik
Sep 12 '17 at 6:16
No. If I click on it, nothing happens. When I hover over it, the message "An exception was caught by the debugger, and user settings indicate that a break should occur" is displayed. I've edited my posting to show this.
– tmighty
Sep 12 '17 at 12:44
add a comment |
When you are in the debugger you can navigate to watch window and use pseudovariables to display some information about the root cause. One particularly useful is $exception.
Check document about pseudovariables.
answered Sep 9 '17 at 18:57
Paweł ŁukasikPaweł Łukasik
2,30411322
When the problem occurs, the IDE tells me "Unable to evaluate the expression.". I've updated my post with the screenshot of it.
– tmighty
Sep 11 '17 at 23:30
Is there no info if you click on 'Stop at Exception' on the right hand side of the Visual Studio?
– Paweł Łukasik
Sep 12 '17 at 6:16
No. If I click on it, nothing happens. When I hover over it, the message "An exception was caught by the debugger, and user settings indicate that a break should occur" is displayed. I've edited my posting to show this.
– tmighty
Sep 12 '17 at 12:44
add a comment |
When you are in the debugger you can navigate to watch window and use pseudovariables to display some information about the root cause. One particularly useful is $exception.
Check document about pseudovariables.
answered Sep 9 '17 at 18:57
Paweł ŁukasikPaweł Łukasik
2,30411322
When you are in the debugger you can navigate to watch window and use pseudovariables to display some information about the root cause. One particularly useful is $exception.
Check document about pseudovariables.
answered Sep 9 '17 at 18:57
Paweł ŁukasikPaweł Łukasik
2,30411322
answered Sep 9 '17 at 18:57
Paweł ŁukasikPaweł Łukasik
2,30411322
answered Sep 9 '17 at 18:57
Paweł ŁukasikPaweł Łukasik
2,30411322
answered Sep 9 '17 at 18:57
Paweł ŁukasikPaweł Łukasik
2,30411322
2,30411322
When the problem occurs, the IDE tells me "Unable to evaluate the expression.". I've updated my post with the screenshot of it.
– tmighty
Sep 11 '17 at 23:30
Is there no info if you click on 'Stop at Exception' on the right hand side of the Visual Studio?
– Paweł Łukasik
Sep 12 '17 at 6:16
No. If I click on it, nothing happens. When I hover over it, the message "An exception was caught by the debugger, and user settings indicate that a break should occur" is displayed. I've edited my posting to show this.
– tmighty
Sep 12 '17 at 12:44
add a comment |
When the problem occurs, the IDE tells me "Unable to evaluate the expression.". I've updated my post with the screenshot of it.
– tmighty
Sep 11 '17 at 23:30
Is there no info if you click on 'Stop at Exception' on the right hand side of the Visual Studio?
– Paweł Łukasik
Sep 12 '17 at 6:16
No. If I click on it, nothing happens. When I hover over it, the message "An exception was caught by the debugger, and user settings indicate that a break should occur" is displayed. I've edited my posting to show this.
– tmighty
Sep 12 '17 at 12:44
When the problem occurs, the IDE tells me "Unable to evaluate the expression.". I've updated my post with the screenshot of it.
– tmighty
Sep 11 '17 at 23:30
When the problem occurs, the IDE tells me "Unable to evaluate the expression.". I've updated my post with the screenshot of it.
– tmighty
Sep 11 '17 at 23:30
Is there no info if you click on 'Stop at Exception' on the right hand side of the Visual Studio?
– Paweł Łukasik
Sep 12 '17 at 6:16
Is there no info if you click on 'Stop at Exception' on the right hand side of the Visual Studio?
– Paweł Łukasik
Sep 12 '17 at 6:16
No. If I click on it, nothing happens. When I hover over it, the message "An exception was caught by the debugger, and user settings indicate that a break should occur" is displayed. I've edited my posting to show this.
– tmighty
Sep 12 '17 at 12:44
No. If I click on it, nothing happens. When I hover over it, the message "An exception was caught by the debugger, and user settings indicate that a break should occur" is displayed. I've edited my posting to show this.
– tmighty
Sep 12 '17 at 12:44
add a comment |
I didn't find any way to actually debug the problem.
I solved the problem the bruteforce way:
I removed all assemblies and COM objects one by one until the error was gone.
In my case, I had a public control with a WithEvents in a module.
It seems that VB.NET didn't like that at all.
From now on, I will put the control and its withevent in a form.
The main problem however remains: Visual Studio doesn't offer any help to isolate the problem easily.
answered Sep 21 '17 at 20:19
tmightytmighty
2,2171058128
add a comment |
I didn't find any way to actually debug the problem.
I solved the problem the bruteforce way:
I removed all assemblies and COM objects one by one until the error was gone.
In my case, I had a public control with a WithEvents in a module.
It seems that VB.NET didn't like that at all.
From now on, I will put the control and its withevent in a form.
The main problem however remains: Visual Studio doesn't offer any help to isolate the problem easily.
answered Sep 21 '17 at 20:19
tmightytmighty
2,2171058128
add a comment |
I didn't find any way to actually debug the problem.
I solved the problem the bruteforce way:
I removed all assemblies and COM objects one by one until the error was gone.
In my case, I had a public control with a WithEvents in a module.
It seems that VB.NET didn't like that at all.
From now on, I will put the control and its withevent in a form.
The main problem however remains: Visual Studio doesn't offer any help to isolate the problem easily.
answered Sep 21 '17 at 20:19
tmightytmighty
2,2171058128
I didn't find any way to actually debug the problem.
I solved the problem the bruteforce way:
I removed all assemblies and COM objects one by one until the error was gone.
In my case, I had a public control with a WithEvents in a module.
It seems that VB.NET didn't like that at all.
From now on, I will put the control and its withevent in a form.
The main problem however remains: Visual Studio doesn't offer any help to isolate the problem easily.
answered Sep 21 '17 at 20:19
tmightytmighty
2,2171058128
edited Sep 22 '17 at 10:07
answered Sep 21 '17 at 20:19
tmightytmighty
2,2171058128
answered Sep 21 '17 at 20:19
tmightytmighty
2,2171058128
answered Sep 21 '17 at 20:19
tmightytmighty
2,2171058128
2,2171058128
add a comment |
add a comment |
This can also occur when a single threaded Winforms application takes more than 60 seconds to complete an action in the main thread.
I solved it in the dirty way, by calling Application.DoEvents() on regular intervals from the main thread, during too long processing. Exceptions that occur between Application.DoEvents calls are handled properly in the IDE.
answered Dec 23 '17 at 3:09
GoodiesGoodies
42828
1
Is this behaviour documented anywhere?
– cbailiss
Nov 25 '18 at 7:35
add a comment |
This can also occur when a single threaded Winforms application takes more than 60 seconds to complete an action in the main thread.
I solved it in the dirty way, by calling Application.DoEvents() on regular intervals from the main thread, during too long processing. Exceptions that occur between Application.DoEvents calls are handled properly in the IDE.
answered Dec 23 '17 at 3:09
GoodiesGoodies
42828
1
Is this behaviour documented anywhere?
– cbailiss
Nov 25 '18 at 7:35
add a comment |
This can also occur when a single threaded Winforms application takes more than 60 seconds to complete an action in the main thread.
I solved it in the dirty way, by calling Application.DoEvents() on regular intervals from the main thread, during too long processing. Exceptions that occur between Application.DoEvents calls are handled properly in the IDE.
answered Dec 23 '17 at 3:09
GoodiesGoodies
42828
This can also occur when a single threaded Winforms application takes more than 60 seconds to complete an action in the main thread.
I solved it in the dirty way, by calling Application.DoEvents() on regular intervals from the main thread, during too long processing. Exceptions that occur between Application.DoEvents calls are handled properly in the IDE.
answered Dec 23 '17 at 3:09
GoodiesGoodies
42828
answered Dec 23 '17 at 3:09
GoodiesGoodies
42828
answered Dec 23 '17 at 3:09
GoodiesGoodies
42828
answered Dec 23 '17 at 3:09
GoodiesGoodies
42828
42828
1
Is this behaviour documented anywhere?
– cbailiss
Nov 25 '18 at 7:35
add a comment |
1
Is this behaviour documented anywhere?
– cbailiss
Nov 25 '18 at 7:35
1
1
Is this behaviour documented anywhere?
– cbailiss
Nov 25 '18 at 7:35
Is this behaviour documented anywhere?
– cbailiss
Nov 25 '18 at 7:35
add a comment |
Go to exception settings and uncheck "Magaged Debugging Assistants"
answered Jun 27 '18 at 1:55
user3578181user3578181
1,3651010
add a comment |
Go to exception settings and uncheck "Magaged Debugging Assistants"
answered Jun 27 '18 at 1:55
user3578181user3578181
1,3651010
add a comment |
Go to exception settings and uncheck "Magaged Debugging Assistants"
answered Jun 27 '18 at 1:55
user3578181user3578181
1,3651010
Go to exception settings and uncheck "Magaged Debugging Assistants"
answered Jun 27 '18 at 1:55
user3578181user3578181
1,3651010
answered Jun 27 '18 at 1:55
user3578181user3578181
1,3651010
answered Jun 27 '18 at 1:55
user3578181user3578181
1,3651010
answered Jun 27 '18 at 1:55
user3578181user3578181
1,3651010
1,3651010
add a comment |
add a comment |
This can occur because some method or constructor is inaccessible (private or internal), put the as public.
The XAML need call the methods to start application
answered Dec 14 '17 at 16:36
impactroimpactro
13114
add a comment |
This can occur because some method or constructor is inaccessible (private or internal), put the as public.
The XAML need call the methods to start application
answered Dec 14 '17 at 16:36
impactroimpactro
13114
add a comment |
This can occur because some method or constructor is inaccessible (private or internal), put the as public.
The XAML need call the methods to start application
answered Dec 14 '17 at 16:36
impactroimpactro
13114
This can occur because some method or constructor is inaccessible (private or internal), put the as public.
The XAML need call the methods to start application
answered Dec 14 '17 at 16:36
impactroimpactro
13114
answered Dec 14 '17 at 16:36
impactroimpactro
13114
answered Dec 14 '17 at 16:36
impactroimpactro
13114
answered Dec 14 '17 at 16:36
impactroimpactro
13114
13114
add a comment |
add a comment |
Thanks for contributing an answer to Stack Overflow!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f46102963%2fthe-application-is-in-break-mode-unable-to-determine-cause%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Please view the task manager, and check that whether certain processes which were related to the debugger tool/this project were not closed, you could close them, and then view the debugging result, or just restart your machine, re-open the project, debug it again. Make sure and run a "clean" under build, or you could get certain compiled error or exception in your side.
– Jack Zhai-MSFT
Sep 8 '17 at 9:39
@JackZhai-MSFT Please explain more in detail what I should do.
– tmighty
Sep 12 '17 at 22:26
1
It looks pretty unhealthy. The finalizer thread is no longer running but there are still three threads running managed code. Not good. Crystal ball says that you noticed the two second timeout at program termination, a hint that the finalizer thread was deadlocked. You have a good reason to contact your component vendor's support, Essential Objects is in the business of supplying risky code that is likely to cause finalizer thread deadlocks.
– Hans Passant
Sep 13 '17 at 8:35
When I faced a similar issue, my problem turned out to be a forgotten break point on a threaded method. Disabling all break points prior to running your app could prove or disprove this theory. Can't remember if my break point was in a referenced project, but it was definitely related.
– blaze_125
Sep 19 '17 at 21:01