OutOfMemoryError when using shared elements transition (EnterTransitionCoordinator) [37066733]

Duplicate

of 37042900

Bug

[AOSP] duplicate

[AOSP] assigned

NeedsInfo

Status Update

No update yet.

Description

jo...@gmail.com

created issue #1

Oct 15, 2015 01:42PM

Using AcvtivityTransition of a ImageView causes a crash when clicked and backed several times in a row (10-20 times). It crashes due to Out Of Memory. By looking at the code it looks like a reference to the image is kept in EnterTransitionCoordinator.mSharedElementsBundle

The problem seems to be similar to this issue

https://code.google.com/p/android-developer-preview/issues/detail?id=1543 but since it was fixed in this commit

https://android.googlesource.com/platform/frameworks/base/+/a0a0260e48e1ee4e9b5d98b49571e8d2a6fd6c3a the problem was transfered to EnterTransitionCoordinator instead.

SDK: 23
Device: Genymotion 5.2.5 running Android 5.1.0
expected: not to crash
actual: crashes after repeated 10-20 times due to due to OOEM

stacktrace
10-15 15:05:26.284 21494-21494/

com.tvnu.app E/AndroidRuntime: java.lang.OutOfMemoryError: Failed to allocate a 2592012 byte allocation with 2082020 free bytes and 2033KB until OOM
10-15 15:05:26.284 21494-21494/

com.tvnu.app E/AndroidRuntime: at dalvik.system.VMRuntime.newNonMovableArray(Native Method)
10-15 15:05:26.284 21494-21494/

com.tvnu.app E/AndroidRuntime: at android.graphics.Bitmap.nativeCreate(Native Method)
10-15 15:05:26.284 21494-21494/

com.tvnu.app E/AndroidRuntime: at android.graphics.Bitmap.createBitmap(Bitmap.java:812)
10-15 15:05:26.284 21494-21494/

com.tvnu.app E/AndroidRuntime: at android.graphics.Bitmap.createBitmap(Bitmap.java:789)
10-15 15:05:26.284 21494-21494/

com.tvnu.app E/AndroidRuntime: at android.graphics.Bitmap.createBitmap(Bitmap.java:756)
10-15 15:05:26.284 21494-21494/

com.tvnu.app E/AndroidRuntime: at android.transition.TransitionUtils.createViewBitmap(TransitionUtils.java:165)
10-15 15:05:26.284 21494-21494/

com.tvnu.app E/AndroidRuntime: at android.app.SharedElementCallback.onCaptureSharedElementSnapshot(SharedElementCallback.java:177)
10-15 15:05:26.284 21494-21494/

com.tvnu.app E/AndroidRuntime: at android.app.ActivityTransitionCoordinator.captureSharedElementState(ActivityTransitionCoordinator.java:767)
10-15 15:05:26.284 21494-21494/

com.tvnu.app E/AndroidRuntime: at android.app.ActivityTransitionCoordinator.captureSharedElementState(ActivityTransitionCoordinator.java:690)
10-15 15:05:26.284 21494-21494/

com.tvnu.app E/AndroidRuntime: at android.app.EnterTransitionCoordinator$3.onPreDraw(EnterTransitionCoordinator.java:204)
10-15 15:05:26.284 21494-21494/

com.tvnu.app E/AndroidRuntime: at android.view.ViewTreeObserver.dispatchOnPreDraw(ViewTreeObserver.java:944)
10-15 15:05:26.284 21494-21494/

com.tvnu.app E/AndroidRuntime: at android.view.ViewRootImpl.performTraversals(ViewRootImpl.java:1970)
10-15 15:05:26.284 21494-21494/

com.tvnu.app E/AndroidRuntime: at android.view.ViewRootImpl.doTraversal(ViewRootImpl.java:1061)
10-15 15:05:26.284 21494-21494/

com.tvnu.app E/AndroidRuntime: at android.view.ViewRootImpl$TraversalRunnable.run(ViewRootImpl.java:5885)
10-15 15:05:26.284 21494-21494/

com.tvnu.app E/AndroidRuntime: at android.view.Choreographer$CallbackRecord.run(Choreographer.java:767)
10-15 15:05:26.284 21494-21494/

com.tvnu.app E/AndroidRuntime: at android.view.Choreographer.doCallbacks(Choreographer.java:580)
10-15 15:05:26.284 21494-21494/

com.tvnu.app E/AndroidRuntime: at android.view.Choreographer.doFrame(Choreographer.java:550)
10-15 15:05:26.284 21494-21494/

com.tvnu.app E/AndroidRuntime: at android.view.Choreographer$FrameDisplayEventReceiver.run(Choreographer.java:753)
10-15 15:05:26.284 21494-21494/

com.tvnu.app E/AndroidRuntime: at android.os.Handler.handleCallback(Handler.java:739)
10-15 15:05:26.284 21494-21494/

com.tvnu.app E/AndroidRuntime: at android.os.Handler.dispatchMessage(Handler.java:95)
10-15 15:05:26.284 21494-21494/

com.tvnu.app E/AndroidRuntime: at android.os.Looper.loop(Looper.java:135)
10-15 15:05:26.284 21494-21494/

com.tvnu.app E/AndroidRuntime: at android.app.ActivityThread.main(ActivityThread.java:5254)
10-15 15:05:26.284 21494-21494/

com.tvnu.app E/AndroidRuntime: at java.lang.reflect.Method.invoke(Native Method)
10-15 15:05:26.284 21494-21494/

com.tvnu.app E/AndroidRuntime: at java.lang.reflect.Method.invoke(Method.java:372)
10-15 15:05:26.284 21494-21494/

com.tvnu.app E/AndroidRuntime: at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:903)
10-15 15:05:26.284 21494-21494/

com.tvnu.app E/AndroidRuntime: at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:698)

Comments

sy...@google.com <sy...@google.com> #2Oct 15, 2015 03:05PM

Assigned to sy...@google.com.

Can you post me the test app source code and steps to reproduce the issue?

fe...@gmail.com <fe...@gmail.com> #3Dec 4, 2015 07:02PM

Sample app attached

Tap on screen to trigger transition, then hit back button to go back. Repeat this multiple times, watch memory consumption grow. App will quickly reach memory limits and sometimes it may crash; other times, OS appears to free some resources, but mem usage is still very high.

deleted

Restricted

0 B

fe...@gmail.com <fe...@gmail.com> #4Dec 4, 2015 10:25PM

Overriding the SharedElementCallback and wrapping the snapshots such that they are clearable mitigates this issue

Here's some sample code:

https://gist.github.com/fesago90/ae7a56628c35e65ddaab

sy...@google.com <sy...@google.com> #5Dec 7, 2015 03:29PM

Hi,

Thank you very much for getting back to us with the requested information. We are working on this issue and will provide updates as they are available.

Thanks..

sy...@google.com <sy...@google.com> Dec 8, 2015 06:11AM

Status: Duplicate of

37042900

jo...@gmail.com <jo...@gmail.com> #6Dec 8, 2015 07:07AM

#2 Thank you for adding a sample! I totally forgot about that!

co...@gmail.com <co...@gmail.com> #7Aug 4, 2016 02:45PM

Is this issue resolved??

[Deleted User] <[Deleted User]> #8Mar 1, 2017 01:10PM

[Comment deleted]

mi...@gmail.com <mi...@gmail.com> #9Mar 1, 2017 01:12PM

How has this still not been resolved? Can we get a progress update, or something?

[Deleted User] <[Deleted User]> #10Jun 6, 2017 03:03PM

I would also be interested in the resolution of this issue. Thanks in advanced