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 7586 [details]
Stacktrace and GDB
We hit this somewhat intermittently after an nunit test case completes.
Expected: Clean exit.
Actual: Attached, mono-sgen processes on the target machine do not exit.
gdb does not provide useful output.
Cannot repro on the target machine with test cases from https://bugzilla.xamarin.com/show_bug.cgi?id=13813 or https://bugzilla.xamarin.com/show_bug.cgi?id=14339
Can you confirm that the crash occurs on mono master?
Could you provide a test case?
The issue is (seemingly) sporadic enough that I haven't been able to capture it in a test case yet, but it is constantly blocking cycle testing.
I'm running with recent builds of the 3.6 and 3.8 branches of mono. I may need to find a runtime team member to help diagnose if it continues blocking.
Would you mind checking if the bug persists if you use the environment variable
Mono doesn't seem to think that's a legitimate option.
>Runtime Environment -
> OS Version: Unix 184.108.40.206
> CLR Version: 2.0.50727.1433 ( Mono 3.5 ( 3.8.0 ((no/62a857e Wed Aug 13 00:46:20 EDT 2014) ) )
>ProcessModel: Default DomainUsage: Single
>Execution Runtime: mono-3.5
>Warning: In environment variable `MONO_GC_PARAMS': Unknown option `clear-at-gc`. - Ignoring.
I'm sorry, it's MONO_GC_DEBUG, not MONO_GC_PARAMS.
Hi Sean, I'm closing this bug as it applies to an older version of Mono. Feel free to reopen if you come across the same problem in our 4.0 or 4.2 releases.