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.
Description of Problem:
first created a new solution then selected android application and then pressed the button to debug the application to run as a test on the device (nexus 4).
The application does not start, the screen just flashes and then back to the home screen!
Testing the same application on the emulator, everything works correctly.
Steps to reproduce the problem:
How often does this happen?
Error log on exit app:
Forwarding debugger port 8881
Forwarding console port 8882
Detecting existing process
[libc] WARNING: generic atexit() called from legacy shared library
[monodroid-gc] GREF GC Threshold: 46800
Loaded assembly: /data/data/test.test/files/.__override__/test.dll
Loaded assembly: Mono.Android.dll [External]
[libc] bionic/libc/upstream-netbsd/libc/stdlib/bsearch.c:70: bsearch: assertion "key != NULL" failed
[mono-rt] Got a SIGSEGV while executing native code. This usually indicates
[mono-rt] a fatal error in the mono runtime or one of the native libraries
[mono-rt] used by your application.
This should be fixed in the current stable Xamarin.Android 4.8.1 release.
*** This bug has been marked as a duplicate of bug 13460 ***