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.
This happens once in a while when running the watchOS System tests in the simulator with the debugger.
Native backtrace for all threads: https://gist.github.com/rolfbjarne/2d8f42d8f064157673d984aaf542deb0
Application output: https://gist.github.com/rolfbjarne/3b63a2fd3e211a66bae9c5ea64bdb315
I can reproduce this fairly easily by opening xamarin-macios/tests/bcl-tests/System-watchos.sln in XS, and running the System-watchos-app project.
Can you look at this suspend bug?
@Rolf does this still happens ? if so can you reply to Ludovic ? thanks!
I run into bug #50117 now.
The crash from 50117 happens before the deadlock, so we can't test whether this bug is still happening until that one is fixed.
I'm not able to reproduce this anymore.