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
{{ message }}
This repository has been archived by the owner on Jul 28, 2020. It is now read-only.
this is a follow up Issue to #413
While the memory leak of Issue 413 is fixed there are still objects which allocation count rises with each session.
Details:
I have found a memory leak when closing a session. (stopping & destroying the ArCore activity)
found using the Android Profiler.
Total memory has increased. There are some objects with names like "bfs", "bao", "arz", etc. that get increased by 1 after a session was opened.
The allocation count starts at 3 so in the first session the allocation count is 3 in the next 4 and so on.
So after opening a session 3 times these objects have an allocation count of 5.
note: the object with name "bys" is always 3 times the number and "bpa" is always double.
First session:
3rd session:
11th session:
this is tested in HelloScenform sample and other ArCore apps.
the memory leak happens every time the Activity is destroyed.
it never happens if the Activity is saved and stopped.
the increase in memory is much smaller with 1.7 than it was in 1.6 thanks to the fix in #413 i assume.
The text was updated successfully, but these errors were encountered:
I am experiencing the same issue.
The hellosceneform profile results. I launched and finished several HelloSceneformActivities one by one. And all of the objects: CameraTextureScene remains in memory after forcing GC: https://monosnap.com/file/ewEPKAHXgPRDQRo6JhGRwCuXhcZutl
These objects holds an an ArSceneView that is why HelloSceneformActivitiy leaked.
Moreover I found that with using asyncPause() feature my Pixel3 reports an error:
E/ACameraDevice: onDeviceIdle sending state cb
E/ActivityThread: Activity %app_package_my_activity% has leaked ServiceConnection apy@e18bb27 that was originally bound here
android.app.ServiceConnectionLeaked: Activity %app_package_my_activity% has leaked ServiceConnection apy@e18bb27 that was originally bound here
at android.app.LoadedApk$ServiceDispatcher.<init>(LoadedApk.java:1610)
at android.app.LoadedApk.getServiceDispatcher(LoadedApk.java:1502)
at android.app.ContextImpl.bindServiceCommon(ContextImpl.java:1659)
at android.app.ContextImpl.bindService(ContextImpl.java:1612)
at android.content.ContextWrapper.bindService(ContextWrapper.java:698)
at com.google.ar.core.services.AnalyticsClient.bindService(PG:30)
at com.google.ar.core.Session.nativeCreateSessionWithFeatures(Native Method)
at com.google.ar.core.Session.<init>(Session.java:23)
It seems that all the samples and scene-form itself was not designed for releasing resources.
this is a follow up Issue to #413
While the memory leak of Issue 413 is fixed there are still objects which allocation count rises with each session.
Details:
I have found a memory leak when closing a session. (stopping & destroying the ArCore activity)
found using the Android Profiler.
Total memory has increased. There are some objects with names like "bfs", "bao", "arz", etc. that get increased by 1 after a session was opened.
The allocation count starts at 3 so in the first session the allocation count is 3 in the next 4 and so on.
So after opening a session 3 times these objects have an allocation count of 5.
note: the object with name "bys" is always 3 times the number and "bpa" is always double.
First session:
![sample_after_first_open](https://user-images.githubusercontent.com/38068535/52956135-be255100-338e-11e9-8f2c-696d0ac3251b.png)
3rd session:
![sample_after_opening_3times](https://user-images.githubusercontent.com/38068535/52956139-c1204180-338e-11e9-9180-6343299562a1.png)
11th session:
![sample_after_opening_11times](https://user-images.githubusercontent.com/38068535/52956143-c3829b80-338e-11e9-8f8e-991bd662008e.png)
this is tested in HelloScenform sample and other ArCore apps.
the memory leak happens every time the Activity is destroyed.
it never happens if the Activity is saved and stopped.
the increase in memory is much smaller with 1.7 than it was in 1.6 thanks to the fix in #413 i assume.
The text was updated successfully, but these errors were encountered: