You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We are seeing a crash in a large app deployment that has only been reproduced in the field. So we only have the stack trace.
This is with an older version of MapLibre on Android. Best to see if it still applies.
After looking at it with Tim this appears to be a corrupt string being used as a key in a map. Also this is in v10 and we'd need to reproduce it in v11 to have any idea what might be causing it. Putting into hibernation for the moment.
More broadly, it's pure memory corruption. The other members near the key can also get corrupted.
Tim is trying some guard bytes and logic with the user's deployment to see if that mitigates it. But we still don't have a cause.
We are seeing a crash in a large app deployment that has only been reproduced in the field. So we only have the stack trace.
This is with an older version of MapLibre on Android. Best to see if it still applies.
The text was updated successfully, but these errors were encountered: