Obsolete
Status Update
No update yet.
Comments
en...@google.com
et...@google.com
nj...@gmail.com
I have met this issuse few weeks ago, and I found that when Layercache::preparedirty, it will use the texture that binded to the fbo which has already missed. So I add a check before use that fbo, and will regenerate the texture if fbo miss attachment.
st...@gmail.com
Is there any progress about this question?
I reproduce this question in my android4.2 phone;
I reproduce this question in my android4.2 phone;
sh...@gmail.com
is there any progress about this?
I also reproduce the issue in my android4.3 device
I also reproduce the issue in my android4.3 device
ni...@gmail.com
so wtf is this?
sa...@google.com
Thank you for your feedback. We have tried our best to address the issue reported, however our product team has shifted work priority which doesn't include this issue. For now, we will be closing the issue as "Won't Fix (Obsolete)". If this issue still currently exists, we request that you log a new issue along with the latest bug report here: https://goo.gl/TbMiIO and reference this bug for context.
Description
Steps to Reproduce:
1.Launch default camera in landscape mode.
2.Press home button.
3.Repeat step 1 & 2 more than 5 times
The following is part of the log,
###############
12-18 08:11:29.710 25632 26063 I GLRootView: GLObject has changed from com.google.android.gles_jni.GLImpl@211d5d68 to com.google.android.gles_jni.GLImpl@21228590
12-18 08:11:29.720 25632 26063 I GLRootView: onSurfaceChanged: 480x320, gl10: com.google.android.gles_jni.GLImpl@21228590
12-18 08:11:29.720 25632 26063 I GLRootView: layout content pane 320x480 (compensation 0)
12-18 08:11:29.720 25632 26063 D PhotoView: compensation = 0, CameraRelativeFrame = Rect(0, 240 - 0, 240), mCameraRect = Rect(0, 240 - 0, 240)
12-18 08:11:29.770 25632 26063 I GLRootView: onSurfaceChanged: 320x480, gl10: com.google.android.gles_jni.GLImpl@21228590
12-18 08:11:29.810 25632 25632 D HardwareRenderer: EGL createContext com.google.android.gles_jni.EGLContextImpl@802d9c50
12-18 08:11:29.830 25632 25632 D HardwareRenderer: EGL makeCurrent com.google.android.gles_jni.EGLContextImpl@802d9c50
12-18 08:11:29.920 25632 25632 D ActivityBase: set CameraRelativeFrame as Rect(0, 19 - 375, 300)
12-18 08:11:29.920 25632 25632 D PhotoView: compensation = 0, CameraRelativeFrame = Rect(0, 19 - 375, 300), mCameraRect = Rect(0, 19 - 375, 300)
12-18 08:11:29.930 25632 26063 I GLRootView: onSurfaceChanged: 480x320, gl10: com.google.android.gles_jni.GLImpl@21228590
12-18 08:11:29.930 25632 26063 I GLRootView: layout content pane 480x320 (compensation 0)
12-18 08:11:29.930 25632 26063 D PhotoView: compensation = 0, CameraRelativeFrame = Rect(0, 19 - 375, 300), mCameraRect = Rect(0, 19 - 375, 300)
12-18 08:11:30.090 25632 26199 V camera : Preview size is 416x312
12-18 08:11:30.120 25632 26199 V camera : Preview size is 416x312
12-18 08:11:30.140 25632 26199 V camera : startPreview
12-18 08:11:30.240 25632 25635 D dalvikvm: GC_CONCURRENT freed 10249K, 47% free 14263K/26696K, paused 15ms+6ms, total 179ms
12-18 08:11:30.410 25632 25632 D OpenGLRenderer: frameworks/base/libs/hwui/LayerRenderer.cpp:43:fbo=11171
12-18 08:11:30.410 25632 25632 D OpenGLRenderer: GL error from OpenGLRenderer: 0x506
###################
When error occurs, the old GL context is destroyed and a new GL context is created. But it seems it will replay the old DisplayList created in previous GL context. In the DisplayList, there is a DrawLayer command which will draw the old layer and fbo created in previous context. The fbo is invalid for the new GL context and GL error is arisen.
Is there any clean for old gl resource in the old displayList when glContext is destroyed by TrimMemeory?