Bug 2953 - When MonoDevelop crashes. mono doesn't go away and uses 50% cpu
Summary: When MonoDevelop crashes. mono doesn't go away and uses 50% cpu
Status: RESOLVED FIXED
Alias: None
Product: Xamarin Studio
Classification: Desktop
Component: General ()
Version: 2.8.6
Hardware: Macintosh Mac OS
: --- normal
Target Milestone: ---
Assignee: Bugzilla
URL:
Depends on:
Blocks:
 
Reported: 2012-01-18 10:24 UTC by Nic Wise
Modified: 2012-04-04 19:00 UTC (History)
2 users (show)

Tags:
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:
Status:
RESOLVED FIXED

Description Nic Wise 2012-01-18 10:24:23 UTC
Subject says it all

MD crashes (and I get the OS crash dialog). MD goes away and can be restarted.

Mono sticks around, and has to be hard killed (kill -9 or using Activity Monitor)

Happy to run something to interrogate it, but dont know what. It happens most times that MD crashes (which is 2-3x a day, tho I never lose data, which is good)
Comment 1 Miguel de Icaza [MSFT] 2012-01-18 10:46:42 UTC
What vesion of Mono do you have on your system?

When this happens, can you go into a console, and type this:

mac$ gdb
(gdb) attach PID
(gdb) t a a bt

Where PID is the process ID for the runaway Mono process
Comment 2 Nic Wise 2012-01-18 11:45:17 UTC
Absolutely, will do.

I have whatever the latest is on the beta channel for MD. I installed an Mono update a couple of days ago (maybe late last week?) when I moved from the stable to beta channel.

HOWEVER I think this was happening before that, but I could have been on a mono beta then too (I switch back and forwards a bit)
Comment 3 Mikayla Hutchinson [MSFT] 2012-01-18 13:11:00 UTC
Can you please double-check the Mono version in the About dialog? There was a known issue with 2.10.7 to which this sounds very similar.
Comment 4 Nic Wise 2012-01-21 09:24:03 UTC
Touch wood (WTF?) it hasn't happened today. But I have:


MonoDevelop 2.8.6.2
Installation UUID: 747e4205-cbe7-4950-bb05-38ea22a7b20f
Runtime:
	Mono 2.10.8.1 (tarball Mon Dec 19 15:17:20 EST 2011)
	GTK 2.24.8
	GTK# (2.12.0.0)
Mono for Android not installed
Apple Developer Tools:
	 Xcode 4.2 (828)
	 Build 4D199
Monotouch: 5.1.2.1
Build information:
	Release ID: 20806002
	Git revision: c83797aec2a7fb04edaf17ef0c697e27a8656aed
	Build date: 2012-01-18 22:20:14+0000
Operating System:
	Mac OS X 10.7.2
	Darwin hypermania.lan 11.2.0 Darwin Kernel Version 11.2.0: Tue Aug  9 20:54:00 PDT 2011; root:xnu-1699.24.8~1/RELEASE_X86_64 x86_64
Comment 5 Nic Wise 2012-01-22 13:41:56 UTC
Pleased to report that with the above config, I've had NO crashes ALL weekend. LOVELY. (close the case, IMO)
Comment 6 Nic Wise 2012-01-22 13:56:40 UTC
That said, I did just quit out and hat mtouch hang at 99% CPU used. I tried the gdb attach, but it seg faulted on me. I had to kill -9 it.
Comment 7 Mikayla Hutchinson [MSFT] 2012-04-04 19:00:13 UTC
Marking this bug closed since it was fixed - if you have the problem with mtouch again and have a trace, please open a new bug against mtouch.