Open ptc-aeveritt opened 3 years ago
On further investigation I have found about 6 cases where our library/app was not cleaning up JNI local references. Now these are properly cleaned up I am no longer seeing a crash on the Note9 (testing on other devices is pending). This suggests to me that our library/app + ARCore is very close to the limit.
Could this be related to 1315?
SPECIFIC ISSUE ENCOUNTERED
Crash in ArSession_update when building with ARCore 1.23 or 1.24. App is terminated. Problem not seen when building with ARCore 1.22 or lower, it is also not seen when building with ARCore 1.22 or lower and running on a device with ARCore 1.23 or higher.
Example crash dump:
VERSIONS USED
adb shell getprop ro.build.fingerprint
: samsung/crownltexx/crownlte:10/QP1A.190711.020/N960FXXU8FUD1:user/release-keysSTEPS TO REPRODUCE THE ISSUE
Note: On some rare occasions the crash happens at step 4 but typically only after the AR Activity has been closed once
WORKAROUNDS (IF ANY)
If only I could fine one!
ADDITIONAL COMMENTS
We have observed this issue on multiple Samsung phones but not on all, in addition to the Note 9 detailed above we are seeing this issue on:
The abort message doesn't give much information: 'Check failed: new_size > maxentries (new_size=1024, maxentries=1024) ' We assume that some JNI reference count is being exceeded based on the backtrace, however we can't locate any information pointing to what it might be. The values for new_size and maxentries have been observed as 512, 1024 and 2048 in different runs, however they are most commonly 1024.