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 663 [details]
We use mono-sgen with a software that takes a large amount of memory (usually 6-8gb per run). In mono 2.8.1 and 2.8.2, mono-sgen is able to easily complete this process. However, in the latest versions of mono (including from the daily builds), this does not work, and we seem to ?randomly? generate errors. It seems to be related to threading.
Please provide more details about your environment and a test case that shows your problem as the crash log is not enough to figure out what's wrong.
Optionally, you can enable coredumps and provide us with one.
This bug has been in the NEEDINFO state with no changes for the last 90 days.
Can we put this back into the NEW or CONFIRMED state, or are we still awaiting
If there is no change in the status of this bug over the next two weeks, this
bug will be marked as NORESPONSE.
No further information was provided. This is sgen on mono 2.8, which is ancient, the bug has probably been fixed.