Bug 4237 - [CorDebugger] Monodevelop uses 100% CPU for long time when hitting breakpoint using dotnet debugger
Summary: [CorDebugger] Monodevelop uses 100% CPU for long time when hitting breakpoint...
Alias: None
Product: Xamarin Studio
Classification: Desktop
Component: Debugger ()
Hardware: PC Windows
: Normal normal
Target Milestone: ---
Assignee: Bugzilla
Depends on:
Reported: 2012-04-04 12:32 UTC by James
Modified: 2013-09-16 16:57 UTC (History)
4 users (show)

Is this bug a regression?: ---
Last known good build:

Notice (2018-05-24): bugzilla.xamarin.com is now in read-only mode.

Please join us on Visual Studio Developer Community and in the Xamarin and Mono organizations on GitHub to continue tracking issues. Bugzilla will remain available for reference in read-only mode. We will continue to work on open Bugzilla bugs, copy them to the new locations as needed for follow-up, and add the new items under Related Links.

Our sincere thanks to everyone who has contributed on this bug tracker over the years. Thanks also for your understanding as we make these adjustments and improvements for the future.

Please create a new report on Developer Community or GitHub with your current version information, steps to reproduce, and relevant error messages or log files if you are hitting an issue that looks similar to this resolved bug and you do not yet see a matching new report.

Related Links:

Description James 2012-04-04 12:32:53 UTC
If I attempt to debug an application using Monodevelop in Windows with the DotNet 4 debugger, when the debugger hits a breakpoint it uses 100% of the CPU (I think it is trying to resolve the values of all variables in scope) for a few minutes.
Comment 1 Marius Ungureanu 2013-09-16 16:57:07 UTC
I see this is no longer an issue.