Bug 5361 - [CorDebugger] "Object is in a zombie state" Error in watch window
Summary: [CorDebugger] "Object is in a zombie state" Error in watch window
Alias: None
Product: Xamarin Studio
Classification: Desktop
Component: Debugger ()
Version: unspecified
Hardware: PC Windows
: Low normal
Target Milestone: ---
Assignee: Bugzilla
Depends on:
Reported: 2012-05-27 13:25 UTC by Gary____
Modified: 2013-09-12 04:34 UTC (History)
2 users (show)

Is this bug a regression?: ---
Last known good build:

Pic Showing Error (39.44 KB, image/png)
2012-05-27 13:32 UTC, Gary____

Notice (2018-05-24): bugzilla.xamarin.com is now in read-only mode.

Please join us on Visual Studio Developer Community and in the Xamarin and 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 Links.

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.

Related Links:

Description Gary____ 2012-05-27 13:25:09 UTC
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
Comment 1 Gary____ 2012-05-27 13:32:45 UTC
Created attachment 1970 [details]
Pic Showing Error

Its the same in the local window and the popup inspector in source.
Comment 2 Gary____ 2012-05-27 13:43:04 UTC
These are unit tests run in debug mode as well, in case that makes a difference.
Comment 3 Jeffrey Stedfast 2012-05-29 15:25:43 UTC
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 :-\
Comment 4 Gary____ 2012-05-29 15:51:20 UTC
My work in this area is almost done. I take it I cant use the mono soft debugger with the Microsoft runtime?
Comment 5 Jeffrey Stedfast 2012-05-29 16:10:39 UTC
No, you'll have to use the Mono runtime for debugging
Comment 6 Marius Ungureanu 2013-09-12 04:34:34 UTC
Fixed and will be included in future releases.