Bug 851 - Poor system performance after use of iOS Simulator
Summary: Poor system performance after use of iOS Simulator
Status: RESOLVED DUPLICATE of bug 820
Alias: None
Product: iOS
Classification: Xamarin
Component: General ()
Version: 4.x
Hardware: Macintosh Mac OS
: --- major
Target Milestone: Untriaged
Assignee: Bugzilla
URL:
Depends on:
Blocks:
 
Reported: 2011-09-16 05:49 UTC by Matt Jones
Modified: 2011-09-16 12:23 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 DUPLICATE of bug 820

Description Matt Jones 2011-09-16 05:49:18 UTC
Everytime I launch the debugger, some script (sh) runs and takes 100% of one core. I kill it, everything's back to normal.

To expand on this:

If I quit the app in the simulator, and then close the simulator, the script does not hang - I can't even see it launch.

However if I quit the simulator when my app is running, the script launches and takes 100% of one core.

If I sample sh, I get this output:

Sampling process 3017 for 1 seconds with 1 millisecond of run time between samples

Sampling completed, processing symbols...

Analysis of sampling sh (pid 3017) every 1 millisecond

Process:         sh [3017]

Path:            /bin/sh

Load Address:    0

Identifier:      sh

Version:         ??? (???)

Code Type:       X86-64 (Native)

Parent Process:  ??? [1]

 

Date/Time:       2011-09-09 13:54:44.081 +0100

OS Version:      Mac OS X 10.6.8 (10K549)

Report Version:  6

 

Call graph:

    928 Thread_25989: Main Thread   DispatchQueue_<multiple>

      928 _dyld_start

        928 dyldbootstrap::start(macho_header const*, int, char const**, long)

          928 dyld::_main(macho_header const*, unsigned long, int, char const**, char const**, char const**)

            928 dyld::fastBindLazySymbol(ImageLoader**, unsigned long)

              928 dyldbootstrap::randomizeExecutableLoadAddress(macho_header const*, char const**, unsigned long*)

 

Total number in stack (recursive counted multiple, when >=5):

 

Sort by top of stack, same collapsed (when >= 5):

        dyldbootstrap::randomizeExecutableLoadAddress(macho_header const*, char const**, unsigned long*)        928

 

Binary Images:

    0x7fff5fc00000 -     0x7fff5fc3bdef  dyld 132.1 (???) <486E6C61-1197-CC7C-2197-82CE505102D7> /usr/lib/dyld

Sample analysis of process 3017 written to file /dev/stdout

The 'Open files and ports' output looks like this:

/Users/spreadcomattjones/Library/Application Support/iPhone Simulator/4.3/Applications/795605E3-980D-4231-8FBD-AE2C2CEE313E/TradeClient1.app
/bin/sh
/usr/lib/dyld
/private/tmp/mono-gdb-commands.sHCHpJ
Comment 1 Sebastien Pouliot 2011-09-16 07:37:47 UTC
This looks like a duplicate of bug #820.

Could you tell us:
* your MonoTouch version;
* your MonoDevelop version;
* your OSX version; and
* your XCode version;

Thanks!
Comment 2 Matt Jones 2011-09-16 08:45:43 UTC
OSX 10.6.8
MonoDevelop 2.6.01
MonoTouch 4.07
XCode 3.2.6
Comment 3 Matt Jones 2011-09-16 09:26:48 UTC
I agree it is a duplicate of #820
Comment 4 Sebastien Pouliot 2011-09-16 12:23:50 UTC
Thanks for the information. You'll be added (automatically) on c.c. to any update occuring on bug #820.

*** This bug has been marked as a duplicate of bug 820 ***