Search Issue Tracker
Third Party Issue
Votes
0
Found in [Package]
2.1.8
Issue ID
1265281
Regression
No
[ARFoundation] Constantly resetting ARSession causes an increase in the Native Heap and errors of internal data leak
Repro steps:
1. Open attached project
2. Build and Run on Android
3. Replace the X and Y coordinates in resetARSess.sh with the coords of the reset button on the screen
4. Push the script to the device "adb push /sdcard/"
5. Run the script "adb shell sh /sdcard/resetARSess.sh" or just rapidly press the reset button
6. Observe the results and the log
Actual: Native Heap keeps increasing on every reset and
"DataBuffer: Internal data leak within a DataBuffer object detected! Be sure to explicitly call release() on all DataBuffer extending objects when you are done with them. (internal object: com.google.android.gms.common.data.DataHolder@a5080f9)" errors are reported in the log
Reproducible with: 2019.4.4f1 - ARFooundation 2.1, 2020.1.0b16 - ARFoundation 3.1.3, 2020.2.0a19 - ARFoundation 4.1.0 - preview.5
Tested and reproduce on these devices:
VLNQA00001, Google Pixel 2 (Pixel 2), Android 11, CPU: Snapdragon 835 MSM8998, GPU: Adreno (TM) 540
VLNQA00128, Samsung Galaxy Note8 (SM-N950F), Android 9, CPU: Exynos 9 Octa 8895, GPU: Mali-G71
Add comment
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- PlayerPrefs get corrupted when a minimized fullscreen Player is closed through the Taskbar
- "To Debug, run app with -diag-job-temp-memory-leak-validation cmd line argument. This will output the callstacks of the leaked allocations." warning is printed when JobTempMemoryLeakValidation switch is enabled
- Main Thread stalling when loading Audio Source asset asynchronously while preloading another Audio Source asset
- Material artifacts occur in the Material Preview window when baked lighting is applied to scenes
- “ArgumentOutOfRangeException” after saving, reseting and re-add Default Tile Palette Tools to the list in Preferences window
Resolution Note:
We have reproduced the memory leak and found it to be an issue in Google's ARCore SDK. We have reported the issue to Google.