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 for Bug 6176 on
GitHub or Developer Community if you have new
information to add and do not yet see a matching new report.
If the latest results still closely match this report, you can use the
In special cases on GitHub you might also want the comments:
GitHub Markdown with public comments
The mono implementation of Control.Dispose() sets the is_disposing flag to true but never references it in Dispose or turns it off. Contrast this to the way the MS .NET Control.Dispose() is implemented, where the isdisposing state flag is checked at the start of the method and immediately returns out if it is disposing already, thus breaking any loop.
This can result in endless cycles leading to a stack overflow in applications that do not experience such cycles on the MS CLR.
Mono's implementation also doesn't turn the flag off after disposal is complete, though that is unrelated to this issue.