Notice (2018-05-24): bugzilla.xamarin.com is now in
Please join us on
Visual Studio Developer Community and in the
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
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.
Created attachment 709 [details]
In this case the content analyzer of the program MJ12node
(http://www.majestic12.co.uk) crashes when using SGen GC but works when using Boehm. I'll attach a stacktrace, and I also have a testcase but it expects to find itself from /tmp/mj12/ - couldn't find a way to change this, sorry about it.
Mono version used: Mono JIT compiler version 2.11 (master/aaef22b Sun Oct 16 12:25:22 EEST 2011) - it apparently works with 2.10.5 though.
1. Download http://refic.psimerion.org/mj12_crash.tar (~80MB)
2. Extract to /tmp/
3. Verify that the files are in /tmp/mj12/
4. In /tmp/mj12/, run "mono MJ12barMono.exe tmp/bar.tmp"
Thanks for the test case, I can repro it.
Working on it now.
This is a bug on the precise stack scanning code.
Zoltan, can you take a look at this?
As a workaround set this environment variable: MONO_GC_PARAMS=stack-mark=conservative
Quick update, it crashes with conservative marking too. I'm looking into that crash.
Did you fix this? I can't reproduce it anymore with current git HEAD.
I think this might have been fixed by the I18N fixes, i.e. 2ae5839a82a1c699504b031f98d6621640ff727a.
Yeah, I was thinking so too. It's just that I have a very similar crash case than this still happening so I thought I should ask if it was some other fix than those I18N.
Btw, there are still some patches in that pull request (https://github.com/mono/mono/pull/189) that have not been committed yet. I've been using them for some time now and can confirm that they work well.
189 has been merged.