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.
This is a bug that was reported deep down in #16735
Reported by Craig Minihan, he said:
This code should cause a crash in Mono when run in the debugger under
* CentOS 6.4 x64
* Mono 3.2.8 (tarball)
* MonoDevelop 4.2.2
* CPU: i7, 8GB RAM
Build it, run it (in the debugger), crash. There is a strong relationship
between the number of threads started and the SIGSEGV, too few and all is well.
Setting above ProcessorCount * 3 causes the exception in my env at least.
Repro test case here: https://bugzilla.xamarin.com/attachment.cgi?id=6590
I can't reproduce this with 3.4.0. I get an OutOfMemoryException after a while.
I have repeated the test on 3.4.0 and I no longer see the crash.
I've thrown a bunch of crazy memory allocation stuff at 3.4 and it seems solid to me. So I guess this issue should be closed.