-
Notifications
You must be signed in to change notification settings - Fork 24
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Native graphics crashes (memory corruption?) #707
Comments
Device Name: Android Version App Version Tangram Version
|
I have been going through the google play dev console to see if I could find any pattern in the crashes. There is a much higher volume of native crash reports in the last few days versus the previous several months. I don't know if that means the issue was introduced recently or if usage has been higher recently. Most of the stack traces are one-of's or occasional two-of's. However there were 13 instances of this particular stack trace across a number of devices dating back to April.
|
S6 running Varun's app-dev-debug.apk
|
Crash when attempting to route for me as well using a Nexus 5, running android 4.4.4, on the debug build @tallytalwar sent around
|
S6 running Varun's app-dev-debug.apk
|
Compiling all recent native graphics crashes reported into a single issue since the prevailing theory suggests they are all related due to some sort of memory corruption.
If you experience a native crash please comment below with the following information and a short description of what you were doing right before it crashed (zooming, searching, routing, rotate device, etc.)
App version and Tangram version can be found by enabling the debug menu. To enable the debug menu search for "!!!!!!!!" (8 x !) and then navigate to the settings menu.
The text was updated successfully, but these errors were encountered: