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 firstname.lastname@example.org on google drive ?
Bug #7449 might be related to this one.