Bug 5364 - Monodevelop crashes on windows
Summary: Monodevelop crashes on windows
Alias: None
Product: Xamarin Studio
Classification: Desktop
Component: General ()
Version: unspecified
Hardware: PC Windows
: --- normal
Target Milestone: ---
Assignee: Bugzilla
Depends on:
Reported: 2012-05-27 19:48 UTC by Gary____
Modified: 2016-04-05 18:44 UTC (History)
3 users (show)

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

crash log (166.19 KB, application/octet-stream)
2012-05-27 19:48 UTC, Gary____
additional crash log (416.95 KB, application/octet-stream)
2012-05-27 19:49 UTC, Gary____
New crash log, more info this time (9.44 KB, application/octet-stream)
2012-06-18 07:46 UTC, Gary____

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 Gary____ 2012-05-27 19:48:31 UTC
Created attachment 1972 [details]
crash log

MD has been crashing quite frequently. Sometimes it simply quits without warning, other times I get the standard window pop "attempting to find a solution" and I get offered a choice to debug  it. Choosing this opens VS but it complains about not having debugging symbols and also shows an error "Attempted to read or write protected memory. This is often an indication that other memory is corrupt.."

Most frequently recently the crashes happen just after running a unit test which failed, sometimes when I click the plus to expand the detail in the Unit Test results pad, sometimes a bit after. In this circumstance i tend to get the option to debug rather than a unexpected program quit.

I've attached the logs from the last 2 times. Note ive this project set to the .net 2 framework. One of my classes does show in incidental output of one of the method calls though, im not quite sure why.

MD 3.0.2 Windows 7
Comment 1 Gary____ 2012-05-27 19:49:19 UTC
Created attachment 1973 [details]
additional crash log
Comment 2 Gary____ 2012-06-18 07:46:39 UTC
Created attachment 2076 [details]
New crash log, more info this time

New crash today, more in the log this time. the 'Windows found a problem and is attempting to find a solution' dialogue popped up. Seems to relate to Pango.
Comment 3 Lluis Sanchez 2015-08-20 13:53:27 UTC
Is this still an issue?
Comment 4 Marius Ungureanu 2016-04-05 18:44:31 UTC
This looks like a memory corruption / sigsegv in native land. I've never seen this kind of issue, so closing this bug per lack of activity.