Bug 1621 - MJ12node.exe sometimes deadlocks when using Boehm
Summary: MJ12node.exe sometimes deadlocks when using Boehm
Alias: None
Product: Runtime
Classification: Mono
Component: JIT ()
Version: unspecified
Hardware: PC Linux
: --- normal
Target Milestone: ---
Assignee: Bugzilla
Depends on:
Reported: 2011-10-21 01:16 UTC by Kari Takanen
Modified: 2012-03-30 00:01 UTC (History)
2 users (show)

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

gdb output (78.38 KB, text/plain)
2011-10-21 01:16 UTC, Kari Takanen

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 Kari Takanen 2011-10-21 01:16:18 UTC
Created attachment 741 [details]
gdb output

The program MJ12node (http://www.majestic12.co.uk) sometimes deadlocks when using Boehm GC. Now this could be the same as #1615, I don't know. With SGen it usually happens in the first 30 mins while with Boehm it can happen after 40 hours or so. So the situation is somewhat better with Boehm.

A gdb trace is attached.

Mono version used: Mono JIT compiler version 2.11 (master/63de171 Thu Oct 20
16:59:08 EEST 2011)
OS: Ubuntu 11.10 64-bit

Please let me know if you need more info or debug data.
Comment 1 Zoltan Varga 2012-01-20 21:58:51 UTC
Does this still happen after #1615 got fixed ?
Comment 2 Kari Takanen 2012-03-29 14:20:56 UTC
Nope, haven't seen it happening anymore.
Comment 3 Zoltan Varga 2012-03-30 00:01:13 UTC