Bug 15085 - Errors and leaks from iOS designer
Summary: Errors and leaks from iOS designer
Status: RESOLVED FIXED
Alias: None
Product: Xamarin Studio
Classification: Desktop
Component: iOS Designer ()
Version: Trunk
Hardware: PC Mac OS
: --- normal
Target Milestone: master
Assignee: Bugzilla
URL:
Depends on:
Blocks:
 
Reported: 2013-09-30 17:46 UTC by Mikayla Hutchinson [MSFT]
Modified: 2013-09-30 23:04 UTC (History)
3 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 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:
Status:
RESOLVED FIXED

Description Mikayla Hutchinson [MSFT] 2013-09-30 17:46:15 UTC
I'm seeing the following error from the iOS designer. Probably a local issue (using make run), but it shouldn't be leaking.

objc[44248]: Object 0x7b27c7c0 of class __NSCFNumber autoreleased with no pool in place - just leaking - break on objc_autoreleaseNoPool() to debug
objc[44248]: Object 0x7b27c7c0 of class __NSCFNumber autoreleased with no pool in place - just leaking - break on objc_autoreleaseNoPool() to debug
INFO: DisplayServer message thread is dying due to: System.SystemException: Kernel returned: MACH_RCV_TIMED_OUT (268451843): (ipc/rcv) timed out
  at MonoTouch.Hosting.CheckReturnExtensions.Check (kern_return_t result) [0x00038] in /Users/michael/Mono/md-addins/Xamarin.Designer.iOS/MonoTouch.Hosting/MachPort.cs:393 
  at MonoTouch.Hosting.MachPort.ReceiveRaw (System.Void* messageBuffer, UInt32 bufferSize) [0x00048] in /Users/michael/Mono/md-addins/Xamarin.Designer.iOS/MonoTouch.Hosting/MachPort.cs:126 
  at MonoTouch.Hosting.MachPort.Receive (System.Void* messageBuffer, UInt32 bufferSize, System.Int32& msgId, MonoTouch.Hosting.MachPort& replyPort) [0x0002d] in /Users/michael/Mono/md-addins/Xamarin.Designer.iOS/MonoTouch.Hosting/MachPort.cs:100 
  at MonoTouch.Hosting.DisplayServer.MessageHandler () [0x00161] in /Users/michael/Mono/md-addins/Xamarin.Designer.iOS/MonoTouch.Hosting/DisplayServer.cs:94
Comment 1 Alan McGovern 2013-09-30 18:32:31 UTC
How can i reproduce this? I haven't been able to repro these errors. Is it a shutdown thing? If so we probably don't care.
Comment 2 Alan McGovern 2013-09-30 18:33:12 UTC
Never mind, it triggered while i was writing that response :p
Comment 3 Alan McGovern 2013-09-30 18:38:10 UTC
Added the missing NSAutoReleasePool.
Comment 4 Mikayla Hutchinson [MSFT] 2013-09-30 23:04:48 UTC
Heh, maybe the bug was contagious!