Bug 50003 - Access violation libmonosgen
Summary: Access violation libmonosgen
Alias: None
Product: Runtime
Classification: Mono
Component: General ()
Version: 4.6.0 (C8)
Hardware: PC Windows
: --- normal
Target Milestone: ---
Assignee: Niklas Therning
Depends on:
Reported: 2016-12-14 12:34 UTC by Mikkel Kruse Johnsen
Modified: 2016-12-16 14:33 UTC (History)
3 users (show)

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

Analyze of crash on windows 7 windbg (46.96 KB, text/plain)
2016-12-14 12:34 UTC, Mikkel Kruse Johnsen

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 GitHub or Developer Community 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 Mikkel Kruse Johnsen 2016-12-14 12:34:12 UTC
Created attachment 18883 [details]
Analyze of crash on windows 7 windbg

We see random crashes on Windows 7. It happens sometimes all the time or not at all a whole day.

It happens on "mono_threads_set_shutting_down".

Comment 1 Niklas Therning 2016-12-16 14:30:31 UTC
Do you have some code to reproduce this issue?
Did you build this mono from source or are you using a release build?
Does it happen on the latest 4.8 alphas as well?
Comment 2 Mikkel Kruse Johnsen 2016-12-16 14:33:00 UTC
We have just tracked it down, to be a problem with cairo and the graphic card in the machine.

Running in safe mode will not cause this error.

So I am closing the bug.

It did happen on 4.8 aswell.