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 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.
Sometimes by clicking in the Xamarin Insight screen, I get the System.ObectDisposeException message
Screencast is here http://www.screencast.com/t/hDgLsiZSU
Code is on https://github.com/EifelMono/Tausendblatt
Thanks for the report. Having code to test is always super helpful.
This is a bug in our exception handling, mostly. Although we maintain a GC handle to each view, that doesn't necessarily extend to the values of the properties of each view.
What's happening here is that you're trying to inspect a disposed view (note that you needed to refresh your app, creating a new view hierarchy). Loading its properties is what results in an eventual ObjectDisposedException. If you were to refresh the visual tree in the Inspector client, you'd be good to go again.
On our end, we are mishandling the ObjectDisposedException, letting it propagate and crash your app. I'll fix that.
Longer-term, perhaps we could use exceptions like that as a signal to tell the client (or prompt the user) to refresh the visual tree.
Will be fixed in next release.