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
Developer Community or GitHub 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.
If one accidentally throws an exception during finalization, the runtime just seems to get ripped straight out and there is no crash log or debug output. This can make it very challenging to track down. Breakpoints in the finalizer/dispose logic seem to work on the device, but not in the simulator. Break on exception only seems to work on the device.
The crash occurs on both simulator and device, although I had to exacerbate the issue on device by repeating the repro several times.
Here is the repro (in test form):
public void repro()
private class BadClass : IDisposable
private string foo;
public static void Create()
public void Dispose()
if (foo.Length == 0)
PS. I'm running VS2015 CTP6. Didn't try in XS.
*** This bug has been marked as a duplicate of bug 26786 ***