Notice (2018-05-24): bugzilla.xamarin.com is now in
Please join us on
Visual Studio Developer Community and in the
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
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.
Hi Guys. I'm making used of a CATildeLayer to do some drawing. With the latest MonoTouch 5.x version I get this trivial SIGSEGV that crashes my application on code that hasn't been touched and running on the appstore.
From the native stack trace I can see that it enters a trampoline. I have changed my trampoline setting on the build... I tried increasing it and it still gives me an issue...
-aot "nrgctx-trampolines=5072" -aot "nimt-trampolines=5027" -aot "ntrampolines=5027"
This trampolining, I have to admit still confuses the !@ out of me.
0 JustEnough 0x01a2dec8 mono_handle_native_sigsegv + 456
1 JustEnough 0x01a13894 mono_sigsegv_signal_handler + 428
2 libsystem_c.dylib 0x37bb4539 _sigtramp + 48
3 JustEnough 0x00cbe4f4 JustEnough_IPad_CallSchedule_Calendar_CalendarBaseView_DrawCells_MonoTouch_CoreGraphics_CGContext_System_Drawing_RectangleF_System_Drawing_RectangleF + 5732
4 JustEnough 0x00cc2cc0 JustEnough_IPad_CallSchedule_Calendar_CalendarBaseView_DrawContents_MonoTouch_CoreGraphics_CGContext_System_Drawing_RectangleF + 520
5 JustEnough 0x00cc2a6c JustEnough_IPad_CallSchedule_Calendar_CalendarBaseView_Draw_System_Drawing_RectangleF + 252
6 JustEnough 0x006b5668 wrapper_runtime_invoke_object_runtime_invoke_dynamic_intptr_intptr_intptr_intptr + 200
7 JustEnough 0x01a134b8 mono_jit_runtime_invoke + 2892
8 JustEnough 0x01b0a370 mono_runtime_invoke + 200
9 JustEnough 0x01bc9744 monotouch_trampoline + 3140
10 UIKit 0x31b5df79 -[UIView(CALayerDelegate) drawLayer:inContext:] + 276
11 QuartzCore 0x376a5e1d -[CALayer drawInContext:] + 116
12 QuartzCore 0x377617e5 _ZL18tiled_layer_renderP16_CAImageProviderjjjjPv + 924
13 QuartzCore 0x376f4f29 _ZL21CAImageProviderThreadPjb + 368
14 libdispatch.dylib 0x30c63897 _dispatch_worker_thread2 + 258
15 libsystem_c.dylib 0x37b661cf _pthread_wqthread + 294
16 libsystem_c.dylib 0x37b660a4 start_wqthread + 8
Got a SIGSEGV while executing native code. This usually indicates
a fatal error in the mono runtime or one of the native libraries
used by your application.
There are many kind of trampolines. Unless the crash log reports a lack of a specific one (it will give you a number) then the cause of the issue is likely elsewhere (and augmenting the number of trampolines won't give you anything, just more memory being allocated).
It be helpful to know which version of MonoTouch you used to build your application (the one on the appstore) so we can track all changes between it and the version you using now (5.0.x or 5.1.x ?)
Also we'll likely need a test case that shows the issue. Something around JustEnough_IPad_CallSchedule_Calendar_CalendarBaseView_DrawCells_MonoTouch_CoreGraphics_CGContext_System_Drawing_RectangleF_System_Drawing_RectangleF is causing this crash.
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.
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.