Bug 12494 - Can't inspect t.Exception: The requested operation cannot be completed because the object has been garbage collected.
Summary: Can't inspect t.Exception: The requested operation cannot be completed becaus...
Status: RESOLVED FIXED
Alias: None
Product: Runtime
Classification: Mono
Component: Debugger ()
Version: unspecified
Hardware: Macintosh Mac OS
: --- normal
Target Milestone: ---
Assignee: Zoltan Varga
URL:
Depends on:
Blocks:
 
Reported: 2013-05-31 13:22 UTC by Dan Abramov
Modified: 2015-07-01 10:08 UTC (History)
5 users (show)

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

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 GitHub or 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.

Related Links:
Status:
RESOLVED FIXED

Description Dan Abramov 2013-05-31 13:22:09 UTC
Hi, with Xamarin.iOS 6.3.5.43 I'm unable to inspect task exceptions in the debugger:

http://i.imgur.com/MM1UOvw.png

This is frustrating because I can't see why a particular task failed without CWL-ing the exception.  
There wasn't such problem in Xamarin.iOS 6.2 that uses Mono 2.
Comment 1 Zoltan Varga 2013-06-01 01:09:10 UTC
Fixed in master (8170bf67b1e630a8eb7d3fa0cb7c191c38f5c663), and mobile-master (e39bea435100d185da2fe0363934809737317229).
Comment 2 Dan Abramov 2013-07-25 17:47:50 UTC
Hi, FYI this is still present in today's Stable update.


=== Xamarin Studio ===

Version 4.0.10 (build 7)
Installation UUID: a12ea7ee-6056-4ee5-80fb-b38d90b05195
Runtime:
	Mono 3.2.0 ((no/7c7fcc7)
	GTK 2.24.20
	GTK# (2.12.0.0)
	Package version: 302000000

=== Apple Developer Tools ===

Xcode 4.6.2 (2067.2)
Build 4H1003

=== Xamarin.Mac ===

Xamarin.Mac: Not Installed

=== Xamarin.iOS ===

Version: 6.4.0.2 (Business Edition)
Hash: c9f7659
Branch: 
Build date: 2013-18-07 21:36:03-0400

=== Xamarin.Android ===

Not Installed

=== Build Information ===

Release ID: 400100007
Git revision: f324e2154ee86ae1b6b8483392eddbf418e6381b
Build date: 2013-07-20 06:23:58+0000
Xamarin addins: fe4f180e2386eafc00087ef68c3a580cff4a2592

=== Operating System ===

Mac OS X 10.9.0
Darwin Dan.local 13.0.0 Darwin Kernel Version 13.0.0
    Wed Jul 17 01:22:21 PDT 2013
    root:xnu-2422.1.43~2/RELEASE_X86_64 x86_64
Comment 3 Zoltan Varga 2013-07-25 17:51:10 UTC
Could you create some kind of testcase ?
Comment 4 Dan Abramov 2013-07-25 18:22:26 UTC
For me, this is enough to reproduce:

    var t1 = Task.Run (() => { throw new Exception (); });
    t1.ContinueWith (t => {
        // Can't view t.Exception's InnerException here
        Console.WriteLine ("Hi");
     });
Comment 5 Zoltan Varga 2013-07-25 20:37:34 UTC
-> reopen.
Comment 6 Zoltan Varga 2013-07-25 21:18:36 UTC
I can't reproduce this.
Comment 7 David Karlaš 2015-07-01 10:08:44 UTC
Commit 8170bf67b1e630a8eb7d3fa0cb7c191c38f5c663 in which bug was fixed was not part of Xamarin.iOS 6.4.0.2, which was used to reopen bug. Hence changing state of bug back to fixed.