Bug 30150 - Application crash on iOS when attempting to profile the app
Summary: Application crash on iOS when attempting to profile the app
Status: RESOLVED FIXED
Alias: None
Product: Profiler
Classification: Xamarin
Component: General ()
Version: unspecified
Hardware: PC Mac OS
: --- normal
Target Milestone: ---
Assignee: Rodrigo Moya
URL:
Depends on:
Blocks:
 
Reported: 2015-05-15 17:22 UTC by John Maddalozzo
Modified: 2015-06-08 17:40 UTC (History)
2 users (show)

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


Attachments
Profiler log with device log appended (57.33 KB, text/plain)
2015-05-15 17:22 UTC, John Maddalozzo
Details


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 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 John Maddalozzo 2015-05-15 17:22:03 UTC
Created attachment 11222 [details]
Profiler log with device log appended

Generally regarding crashes trying to profile with XS on iOS.
See https://forums.xamarin.com/discussion/29018/issues?

There were lots of requests for logs...

I'm attaching logs for that. I just upgraded XS today (v5.9.1) and just downloaded and installed the profiler today.
Comment 1 Rodrigo Moya 2015-06-08 17:40:11 UTC
This is a problem in the startup code in our iOS stack, for which we already have a fix internally, which will be published soon to the public channels. So closing this, feel free to reopen if it keeps happening after you have a build with the fix.