Bug 499 - Application output contains many of: "not waiting owns ()" with Monotouch 4.1
Summary: Application output contains many of: "not waiting owns ()" with Monotouch 4.1
Alias: None
Product: iOS
Classification: Xamarin
Component: XI runtime ()
Version: 4.x
Hardware: Macintosh Mac OS
: --- normal
Target Milestone: Untriaged
Assignee: Bugzilla
Depends on:
Reported: 2011-08-28 17:14 UTC by René Ruppert
Modified: 2013-12-05 18:33 UTC (History)
4 users (show)

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 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 René Ruppert 2011-08-28 17:14:52 UTC
With Monotouch 4.1 I get the following output all over the place. There isn't anything specific. It happens for all kinds of occasions and very often.
Not sure if it is really an issue, but it looks like one.

<unnamed thread>" tid=0x0xac80a2c0 this=0x0x9c9bf18 thread handle 0x103 state : not waiting owns ()
  at MonoTouch.ObjCRuntime.Runtime.ConstructNSObject (intptr,intptr) [0x0002e] in /Developer/MonoTouch/Source/monotouch/src/ObjCRuntime/Runtime.cs:199
  at MonoTouch.ObjCRuntime.Runtime.GetNSObject (intptr) [0x0001f] in /Developer/MonoTouch/Source/monotouch/src/ObjCRuntime/Runtime.cs:243
  at MonoTouch.ObjCRuntime.Runtime.GetNSObjectWrapped (intptr) [0x00000] in /Developer/MonoTouch/Source/monotouch/src/ObjCRuntime/Runtime.cs:260
  at (wrapper native-to-managed) MonoTouch.ObjCRuntime.Runtime.GetNSObjectWrapped (intptr) <IL 0x0001f, 0xffffffff>
  at (wrapper managed-to-native) MonoTouch.ObjCRuntime.Messaging.IntPtr_objc_msgSend_IntPtr_IntPtr_IntPtr (intptr,intptr,intptr,intptr,intptr) <IL 0x0002a, 0xffffffff>
  at MonoTouch.Foundation.NSBundle.LoadNib (string,MonoTouch.Foundation.NSObject,MonoTouch.Foundation.NSDictionary) [0x00034] in /Developer/MonoTouch/Source/monotouch/src/Foundation/NSBundle.g.cs:357
  at Flugwetter.AppDelegateBase.FinishedLaunching (MonoTouch.UIKit.UIApplication,MonoTouch.Foundation.NSDictionary) [0x00000] in /Users/Rene/Documents/Develop/Flugwetter/Flugwetter/AppDelegateBase.cs:39
  at Flugwetter.AppDelegateIPhone.FinishedLaunching (MonoTouch.UIKit.UIApplication,MonoTouch.Foundation.NSDictionary) [0x00000] in /Users/Rene/Documents/Develop/Flugwetter/Flugwetter/AppDelegateIPhone.cs:23
  at (wrapper runtime-invoke) <Module>.runtime_invoke_bool__this___object_object (object,intptr,intptr,intptr) <IL 0x00066, 0xffffffff>
  at (wrapper managed-to-native) MonoTouch.UIKit.UIApplication.UIApplicationMain (int,string[],intptr,intptr) <IL 0x0009f, 0xffffffff>
  at MonoTouch.UIKit.UIApplication.Main (string[],string,string) [0x00042] in /Developer/MonoTouch/Source/monotouch/src/UIKit/UIApplication.cs:29
  at MonoTouch.UIKit.UIApplication.Main (string[]) [0x00000] in /Developer/MonoTouch/Source/monotouch/src/UIKit/UIApplication.cs:34
  at Flugwetter.Application.Main (string[]) [0x00000] in /Users/Rene/Documents/Develop/Flugwetter/Flugwetter/Main.cs:13
  at (wrapper runtime-invoke) <Module>.runtime_invoke_void_object (object,intptr,intptr,intptr) <IL 0x00050, 0xffffffff>
Comment 1 Sebastien Pouliot 2011-08-29 14:13:02 UTC
You're seeing the stack traces because newer MonoTouch releases are enabled "E:all" as a debugging option. This will show the stack trace each time an exception is being thrown.

In fact you should be seeing an exception, likely in the few previous log lines, that will say "Selector invoked from objective-c on a managed object that has been GC'ed" and this means a selector was called on an object that the garbage collector has freed.

Don't you get an exception (in your app) and that message printed along the stack trace ?
Comment 2 René Ruppert 2011-08-30 13:07:11 UTC
Can I somehow add this option to MT 4.0.6, because with 4.1 I'm really missing Console output!
Comment 3 Sebastien Pouliot 2011-09-05 15:53:55 UTC
The "E:all" was _removed_ from MonoTouch because they were more confusing (e.g. hidhing important lines) than helpful. AFAIK the Console output issue (which was related to switching to USB debugging) is also fixed.

It's unclear if you still have an issue with the original stack trace (from the description). If so can you provide the Application Output (before the automatic stacktrace) or, if fixed, simply close the bug report? Thanks!
Comment 5 PJ 2013-11-19 17:03:58 UTC
This bug has been in the NEEDINFO state with no changes for the last 90 days. Can we put this back into the NEW or CONFIRMED state, or are we still awaiting response?

If there is no change in the status of this bug over the next two weeks, this bug will be marked as NORESPONSE.
Comment 6 PJ 2013-12-05 18:33:59 UTC
This bug has not been changed from the NEEDINFO state since my previous comment, marking as RESOLVED NORESPONSE.

Please feel free to REOPEN this bug at any time if you are still experiencing the issue. Please add the requested information and set the bug back to the NEW (or CONFIRMED) state.