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.
The inspection tool / watch seems to have limits in how deep it can go into the nested collections of a CodeCompileUnit before it shows an "Object is in a zombie state" Exception from HRESULT: 0x8013134F error.
Windows 7 MD 3.0.2
Created attachment 1970 [details]
Pic Showing Error
Its the same in the local window and the popup inspector in source.
These are unit tests run in debug mode as well, in case that makes a difference.
You'll probably get a much better experience using the Mono Soft debugger instead of the Microsoft .NET debugger in MonoDevelop since that's what all of my focus has been on :-\
My work in this area is almost done. I take it I cant use the mono soft debugger with the Microsoft runtime?
No, you'll have to use the Mono runtime for debugging
Fixed and will be included in future releases.