Bug 8870 - MonoDevelop Crash Viewing SourceCode
Summary: MonoDevelop Crash Viewing SourceCode
Alias: None
Product: Xamarin Studio
Classification: Desktop
Component: C# Binding ()
Version: 3.0.x
Hardware: PC Windows
: High normal
Target Milestone: ---
Assignee: Mike Krüger
Depends on:
Reported: 2012-12-10 10:23 UTC by Allie Miller
Modified: 2012-12-10 23:59 UTC (History)
1 user (show)

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

Translated Crash error (7.93 KB, text/rtf)
2012-12-10 10:23 UTC, Allie Miller

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 Allie Miller 2012-12-10 10:23:17 UTC
Created attachment 3075 [details]
Translated Crash error

Every project that is loaded, including "StandardControls", causes MonoDevelop to crash.

The steps taken that causes the crash is starting Monodevelop--> Monodevelop loads the  last solution (even if no selection or further steps made through mouse or keyboard input) Monodevelop  crashes in few seconds upon opening solution.

This occurs in every source code, every  file, and the application crashes.

The error log is attached to this bug.

Using MonoDevelop 3.0.5
Comment 2 Mikayla Hutchinson [MSFT] 2012-12-10 19:56:02 UTC
Looks like an unobserved task exception in semantic highlighting. It should be possible to work around it by disabling semantic highlighting in preferences.
Comment 3 Mike Krüger 2012-12-10 23:59:40 UTC

I thought I already catched that :/