12-07-2019, 11:41 AM
(12-07-2019, 11:10 AM)yoke_sune Wrote: Still waiting for some indication of if there is a fix on its way, or we're should just live with an unstable application.. I can see that it is hard for you to debug if you cannot replicate it, but seeing we're multiple people having the same issue, then i think this should be prioritized or at least let us help you reproduce it somehow. Did you get anything out of the crash dump etc.?
Hi there,
We're currently actively working on this. So far we have not been able to reliably reproduce it, seems to be related to an issue we're having that only manifests itself on iOS (A12 CPUs), and that boils down to a memory corruption issue. The dump indicates a crash in a very unlikely place in the code, when accessing a pointer that must necessarily point to valid memory as far as logic flow goes. Probably the culprit is somewhere else in the code, but we've yet to discover where.
More info soon, sorry for taking so long to fix this one.