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.
While sorting out an internal customer issue, I tried launching a XM app with MONO_GC_DEBUG=verify-before-collections as suggested.
It crashed right away, so I tried a "hello world" XM app and get the same thing:
Steps to reproduce:
- Install XM
- Xamarin Studio -> New Solution
- Mac -> App -> Cocoa App
- Launch from command line with MONO_GC_DEBUG=verify-before-collections for example:
- Crash and burn.
XM 2.8 gives a different crash than above (without the funny how did we get message).
This should be fixed on master
Do we need to backport it to 4.6?
My fixes weren't applying cleanly on 4.6 due to other previous changes/fixes so I didn't backport them to avoid too many changes. The bug would pop only when using these non-standard debug flags (most of which weren't even working for some time), or when using the profiler with the concurrent collector.
I'm not sure how critical these fixes are. kumpera ?
They don't affect correctness of regular runs. All they do is make our lives easier when debugging sgen issues.