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.
We see around 200 crashes per day with the following callstack (as reported by HockeyApp);
1 libsystem_kernel.dylib __pthread_kill + 8
2 libsystem_pthread.dylib pthread_kill + 60
3 libsystem_c.dylib abort + 74
4 KingsRoad_iOS log_callback (runtime.m:817)
5 KingsRoad_iOS log_adapter (mono-logger.c:278)
6 KingsRoad_iOS monoeg_assertion_message (goutput.c:113)
7 KingsRoad_iOS SleepEx (wthreads.c:93)
8 KingsRoad_iOS monitor_thread (threadpool.c:909)
9 KingsRoad_iOS start_wrapper (threads.c:663)
10 KingsRoad_iOS inner_start_thread (mono-threads-posix.c:88)
11 libsystem_pthread.dylib _pthread_body + 136
12 libsystem_pthread.dylib _pthread_start + 116
13 libsystem_pthread.dylib thread_start + 6
The only code we have even vaguely related to this is where we set the thread pool size;
System.Threading.ThreadPool.SetMaxThreads (6, 4); // default is (200, 8)
System.Threading.ThreadPool.SetMinThreads (6, 4); // default is (2, 4)
We chose these numbers empirically based on measured performance on low-end iOS devices. Specifically these numbers give us the best performance on iPad 2 and iPad Mini 1. Not sure if setting these is even related to the crash however.
App is KingsRoad:
That does not looks like this is coming from the main thread. Do you have a more complete crash report from HockeyApp ?
lookup_thread (HANDLE handle)
ok = _wapi_lookup_handle (handle, WAPI_HANDLE_THREAD,
^ that's the assert being hit
@Rodrigo ever seen something similar ?
Created attachment 9934 [details]
here's a sample report from this crash
Thanks! That gives a lot more information.
David, fwiw this crash does not have any impact on your users, it's crashing when the app is already exiting (iow there is no visible difference for app users).
makes sense; would be nice for the mono shutdown to be 'clean' and not generate a crash report. But this is minor.
This should eventually be addressed by the io-layer work you'd been doing.
We now properly cleanup the monitor thread.