Bug 39471 - Complex console app crashing silently on Mono 4.2.0, running for a while on 4.5, then SIGSEGVing
Summary: Complex console app crashing silently on Mono 4.2.0, running for a while on 4...
Status: NEW
Alias: None
Product: Runtime
Classification: Mono
Component: General ()
Version: unspecified
Hardware: PC Linux
: --- normal
Target Milestone: ---
Assignee: Bugzilla
Depends on:
Reported: 2016-03-08 22:54 UTC by linuxdfmx123
Modified: 2016-03-08 22:54 UTC (History)
2 users (show)

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

SIGSEGV Stack Trace (113.84 KB, text/plain)
2016-03-08 22:54 UTC, linuxdfmx123

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 for Bug 39471 on GitHub or Developer Community if you have new information to add and do not yet see a matching new report.

If the latest results still closely match this report, you can use the original description:

  • Export the original title and description: GitHub Markdown or Developer Community HTML
  • Copy the title and description into the new report. Adjust them to be up-to-date if needed.
  • Add your new information.

In special cases on GitHub you might also want the comments: GitHub Markdown with public comments

Related Links:

Description linuxdfmx123 2016-03-08 22:54:16 UTC
Created attachment 15320 [details]
SIGSEGV Stack Trace

This is a complex console app that spawns 25 worker threads, it works with multiple transient data structures; it deserializes a lot of objects (using Newtonsoft.Json), and it may even create some circular references that put extra burden on the GC. However, the app is fast and stable on Windows. On Mono 4.5, however, it throws a SIGSEGV (see attached stack trace) after running for about 20 minutes. The input to the app can be randomized and the SIGSEGV still happens after 20 minutes, suggesting that some resource is becoming scarce, rather than a specific condition in code being hit. Furthermore, if we create a simple proof-of-concept experiment that calls on the same methods on the same referenced libraries, it will run without issues, which also seems to point to a GC problem. The SIGSEGV and stacktrace are very similar if the app is built on Windows using Visual Studio, or on Linux using xbuild, and has been hit with and without --gc=sgen (which for Mono 4.5 doesn't seem to make any difference). Any ideas are appreciated.