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.
See http://forums.xamarin.com/discussion/comment/124322/#Comment_124322 it looks like at least 2 others see this with the latest Xamarin.
I'm hitting the exact same problem where sometimes I'll have a task that takes 7-8 seconds to start where it normally finishes in 100ms. I only really see the issue in Release which makes it really hard to debug. It doesn't appear to be GC related since when this occurs it takes on the order of 10-20ms. This only recently started happening.
Same problem here. Going back to Mono 3.12 and Xamarin.Android 4.x fixes the problem.
This is affecting our customers in the field.
This might be related to the latest Xamarin.Insights. I'm just tried using the Insights.DebugModeKey in my release builds and it looks like this may have gone away.
Many thanks for the report and the clues about the relation to Xamarin.Insights. I was able to reproduce the problem in a minimal test case that uses Xamarin.Insights. I have filed a new bug with that test case as Bug 30548 to provide a clean starting point for the investigation based on that specific test case.
I suspect the Xamarin developer team can probably resolve this bug as a duplicate of Bug 30548 considering the very close matches in observed results and effective workarounds compared to the original customer reports both on this bug (Bug 30471) and on the forums.
*** This bug has been marked as a duplicate of bug 30548 ***