Bug 7607 - MonoDevelop using a lot of CPU
Summary: MonoDevelop using a lot of CPU
Status: RESOLVED NOT_ON_ROADMAP
Alias: None
Product: Xamarin Studio
Classification: Desktop
Component: General ()
Version: 3.0.x
Hardware: PC Mac OS
: --- normal
Target Milestone: ---
Assignee: Bugzilla
URL:
Depends on:
Blocks:
 
Reported: 2012-10-02 23:53 UTC by Maurício Linhares
Modified: 2012-10-03 15:23 UTC (History)
1 user (show)

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


Attachments
Dumps containing information about the running app. (23.35 KB, application/zip)
2012-10-02 23:54 UTC, Maurício Linhares
Details


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:
Status:
RESOLVED NOT_ON_ROADMAP

Description Maurício Linhares 2012-10-02 23:53:51 UTC
MonoDevelop constantly using 100% CPU on my project whenever I type anything.

I can't easily reproduce this issue, unless I'm at the project I'm working on, but it now happens all the time. I have already disabled aggressive code completition.

Adding a couple of thread dumps of the app running at 100%.
Comment 1 Maurício Linhares 2012-10-02 23:54:20 UTC
Created attachment 2674 [details]
Dumps containing information about the running app.
Comment 2 Maurício Linhares 2012-10-03 00:12:20 UTC
And I reverted back to 3.0.3.5 and the issue doesn't happen. Seems like it's something new at 3.0.4.
Comment 3 Mikayla Hutchinson [MSFT] 2012-10-03 15:23:50 UTC
It looks like you have source analysis enabled. Source analysis has severe performance problems unless you use the sgen garbage collector. Sgen isn't used by default in Mono 2.10.x, but will be on by default in a future version of Mono. We've added a check to the next version of MD that will warn you if you enable source analysis without sgen.

For now you can run MD with sgen by running the following command from a terminal:
mono --gc=sgen /Applications/MonoDevelop.app/Contents/MacOS/lib/monodevelop/bin/MonoDevelop.exe

Beware that it may occasionally crash on startup, or anything else that destroys appdomains (T4, NUnit).

Alternatively you can disable source analysis in Preferences->Other->Source Analysis.