Bug 38997 - App crashes on launch when run with the timing instrument
Summary: App crashes on launch when run with the timing instrument
Status: RESOLVED NORESPONSE
Alias: None
Product: Runtime
Classification: Mono
Component: GC ()
Version: 4.2.0 (C6)
Hardware: PC Windows
: --- normal
Target Milestone: ---
Assignee: Bugzilla
URL:
Depends on:
Blocks:
 
Reported: 2016-02-22 18:09 UTC by Randall Schmidt
Modified: 2017-07-07 14:41 UTC (History)
7 users (show)

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


Attachments
Profiler log (8.44 KB, text/plain)
2016-02-22 18:09 UTC, Randall Schmidt
Details
About Xamarin Studio (1.02 KB, text/plain)
2016-02-22 18:09 UTC, Randall Schmidt
Details
Simulator log (204.31 KB, text/plain)
2016-02-22 18:09 UTC, Randall Schmidt
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 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 NORESPONSE

Description Randall Schmidt 2016-02-22 18:09:14 UTC
Created attachment 15132 [details]
Profiler log

When launching my app with the profiler on the iPad simulator I see the attached crash stack trace in the simulator log. It doesn't always happen, but happens maybe 70% of the time. I do not see this when I'm not using the profiler.

The profiler log doesn't look too interesting but I attached that too.

The crash trace is:

Feb 22 11:50:24 blushweaver nisfpguiMonoTouch[51229]: error: More threads have died (1) that been initialy suspended 0
Feb 22 11:50:24 blushweaver nisfpguiMonoTouch[51229]: critical: Stacktrace:
Feb 22 11:50:24 blushweaver nisfpguiMonoTouch[51229]: critical: 
	Native stacktrace:
Feb 22 11:50:24 blushweaver nisfpguiMonoTouch[51229]: critical: 	0   nisfpguiMonoTouch                   0x006bbc37 mono_handle_native_sigsegv + 311
Feb 22 11:50:24 blushweaver nisfpguiMonoTouch[51229]: critical: 	1   nisfpguiMonoTouch                   0x006c38d1 sigabrt_signal_handler + 145
Feb 22 11:50:24 blushweaver nisfpguiMonoTouch[51229]: critical: 	2   libsystem_platform.dylib            0x04f4d03b _sigtramp + 43
Feb 22 11:50:24 blushweaver nisfpguiMonoTouch[51229]: critical: 	3   ???                                 0xffffffff 0x0 + 4294967295
Feb 22 11:50:24 blushweaver nisfpguiMonoTouch[51229]: critical: 	4   libsystem_c.dylib                   0x04ce365d abort + 156
Feb 22 11:50:24 blushweaver nisfpguiMonoTouch[51229]: critical: 	5   nisfpguiMonoTouch                   0x0086306b _ZL12log_callbackPKcS0_S0_iPv + 91
Feb 22 11:50:24 blushweaver nisfpguiMonoTouch[51229]: critical: 	6   nisfpguiMonoTouch                   0x00835620 log_adapter + 176
Feb 22 11:50:24 blushweaver nisfpguiMonoTouch[51229]: critical: 	7   nisfpguiMonoTouch                   0x00846cfa monoeg_g_log + 106
Feb 22 11:50:24 blushweaver nisfpguiMonoTouch[51229]: critical: 	8   nisfpguiMonoTouch                   0x007c66ff sgen_client_stop_world + 2367
Feb 22 11:50:24 blushweaver nisfpguiMonoTouch[51229]: critical: 	9   nisfpguiMonoTouch                   0x007f8f85 sgen_stop_world + 85
Feb 22 11:50:24 blushweaver nisfpguiMonoTouch[51229]: critical: 	10  nisfpguiMonoTouch                   0x007f88fd sgen_perform_collection + 93
Feb 22 11:50:24 blushweaver nisfpguiMonoTouch[51229]: critical: 	11  nisfpguiMonoTouch                   0x007fa49d sgen_gc_collect + 77
Feb 22 11:50:24 blushweaver nisfpguiMonoTouch[51229]: critical: 	12  nisfpguiMonoTouch                   0x008634a9 _ZL7pump_gcPv + 41
Feb 22 11:50:24 blushweaver nisfpguiMonoTouch[51229]: critical: 	13  libsystem_pthread.dylib             0x04f39c25 _pthread_body + 138
Feb 22 11:50:24 blushweaver nisfpguiMonoTouch[51229]: critical: 	14  libsystem_pthread.dylib             0x04f39b9b _pthread_body + 0
Feb 22 11:50:24 blushweaver nisfpguiMonoTouch[51229]: critical: 	15  libsystem_pthread.dylib             0x04f36e32 thread_start + 34
Feb 22 11:50:24 blushweaver nisfpguiMonoTouch[51229]: critical: 
	=================================================================
	Got a SIGABRT while executing native code. This usually indicates
	a fatal error in the mono runtime or one of the native libraries 
	used by your application.
	=================================================================
Comment 1 Randall Schmidt 2016-02-22 18:09:36 UTC
Created attachment 15133 [details]
About Xamarin Studio
Comment 2 Randall Schmidt 2016-02-22 18:09:52 UTC
Created attachment 15134 [details]
Simulator log
Comment 3 Randall Schmidt 2016-02-22 22:32:32 UTC
FYI I got mixed up with the title and wrote "allocations instrument" when I meant "timing instrument". I edited the title.
Comment 4 Rodrigo Moya 2016-02-23 14:48:17 UTC
This is a crash in the sgen GC, so changing product/component.
Comment 5 Vlad Brezae 2017-07-03 22:07:41 UTC
Hey ! This was a crash in sgen's suspend mechanism which has been completely replaced since. Are you encountering any issues on 5.0 or newer mono ?
Comment 6 Randall Schmidt 2017-07-05 15:06:11 UTC
Hi Vlad, unfortunately I won't be able to check that in the foreseeable future as I'm not working on Xamarin apps anymore.
Comment 7 Ludovic Henry 2017-07-07 14:41:37 UTC
If you ever get the chance to give it a try and find that you can still reproduce it, please feel free to reopen the bug. Thank you!