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.
Are you using the 'Use LLVM optimizing compiler' option ?
We are using LLVM.
And does turning that off fixes the problem ?
Yes, actually, it does.
Is anybody working on this bug? I gather from our discussion that this is a problem with the LLVM compiler. Turning off LLVM is just not an option for us; we are close to release, and as you can imagine, swapping out the compiler at the last minute is a little risky. Can I get an update on what's being done on this issue?
Committed a workaround to mobile-master in 6e2a2668caf337c0e4cbd683d7c561756c4dc3a9.
What does that mean for us? When would this workaround be available in a stable release?
Can somebody answer the question above ?
David: there should be another stable release (with this fix) at latest by the end of next week.
This is not fixed, there is only a workaround. David, could you share the binaries with email@example.com on google drive ?
Bug #7449 might be related to this one.