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.
It crash when debugging , and sometimes in release mode too with this messages :
E/art (12972): Nested signal detected - original signal being reported
F/art (12972): art/runtime/fault_handler.cc:117] Check failed: !initialized_
tried to set Target Android to 23 that didn’t work.
tried running adb shell setprop debug.mono.env
MONO_DEBUG=soft-breakpoints that didn’t work.
tried to compile using different Android API's Versions
ANY IDEA WHY IS THIS HAPPENING ??
HERE IS MY CODE:
public void start()
for (int i = 0; i < 50; i++)
Task.Run(() => RunScanTcp());
//Thread thread = new Thread(new ThreadStart(RunScanTcp));
public void RunScanTcp()
while (abort != true)
port = port + 1;
Log.Info("PORT SCANNER", port.ToString());
Im compiling using :
Android Version (Android 7.1 Nougat)
Minimum Android Version :
Android 4.1 (API Level 16 - Jelly Bean)
Target Android Version:
Compile Using SDK Version
## Bookkeeping note
@Emin, note that it is not recommended to file multiple bug reports with the exact same text for one problem. Response times on bug reports will vary. For certain troubleshooting scenarios, help from the community can be the fastest option. This might or might not be helpful for the particular issue in this bug report. See  and  for a few additional details about various contact options.
*** This bug has been marked as a duplicate of bug 57131 ***