Forums - GLES Driver crash on Nexus 6

4 posts / 0 new
Last post
GLES Driver crash on Nexus 6
pkirill
Join Date: 18 Nov 15
Posts: 5
Posted: Thu, 2015-11-19 01:39

Hi, I have a N6 device with the latest android ndroid 6.0, build MRA58N

I have a test that renders a skinned person with phong shader. 

If I render the model 256 times it works good. When I try to render 1024 times it craches with the followin message:

11-19 12:25:51.386  16817-16848/delightex.androidTest I/Adreno QUALCOMM build                   : 576fcee, I44fb0b5862

    Build Date                       : 08/26/15

    OpenGL ES Shader Compiler Version: XE031.05.13.02

    Local Branch                     : M13

    Remote Branch                    :

    Remote Branch                    :

    Reconstruct Branch               :

11-19 12:25:51.426  16817-16848/delightex.androidTest I/OpenGLRenderer Initialized EGL, version 1.4

11-19 12:25:51.559  16817-16847/delightex.androidTest I/System.out EGLConfig.chooseConfig, display = r8g8b8a8d24s8

11-19 12:25:51.604  16817-16847/delightex.androidTest I/System.out AndroidSceneView onSurfaceCreated: glError = 0

11-19 12:25:51.703  16817-16847/delightex.androidTest I/System.out GL_VENDOR: Qualcomm

11-19 12:25:51.711  16817-16847/delightex.androidTest I/System.out GL_RENDERER: Adreno (TM) 420

11-19 12:25:51.712  16817-16847/delightex.androidTest I/System.out Graphics::Graphics 0, 0, frameBuffer = 0, maxTextureSize = 16384, anisotropicMax = 16.0

11-19 12:25:51.726  16817-16847/delightex.androidTest I/System.out AndroidSceneView onSurfaceChanged : 1440x2392

11-19 12:26:53.902  16817-16847/delightex.androidTest I/System.out AndroidSceneView onSurfaceChanged : 2413x1440

11-19 12:27:18.265  16817-16847/delightex.androidTest I/System.out ResourceLoader:  --> opened address = 0x1e3804, length = 2078960

11-19 12:27:18.289  16817-16847/delightex.androidTest I/System.out Number of animations: 61

11-19 12:27:18.328  16817-16847/delightex.androidTest I/System.out Compiling ShaderCColor, vertex type = Pos

11-19 12:27:18.389  16817-16847/delightex.androidTest I/System.out Compiling ShaderPhongBY, vertex type = Pos, Norm

11-19 12:27:18.452  16817-16847/delightex.androidTest I/System.out Compiling ShaderPhongBYSkinned, vertex type = Pos, Norm, Bone

11-19 12:27:19.392  16817-16847/delightex.androidTest I/System.out AndroidSceneView setSceneLater dt = 1272.219583 millis

11-19 12:27:22.304  16817-16847/delightex.androidTest W/Adreno-GSL <gsl_ldd_control:466>: ioctl fd 24 code 0x400c0907 (IOCTL_KGSL_DEVICE_WAITTIMESTAMP_CTXTID) failed: errno 35 Resource deadlock would occur

11-19 12:27:22.304  16817-16847/delightex.androidTest W/Adreno-GSL <log_gpu_snapshot:375>: panel.gpuSnapshotPath is not set.not generating user snapshot

11-19 12:27:22.304  16817-16847/delightex.androidTest W/Adreno-GSL <gsl_umd_context_waittimestamp:267>: error:-12 ctx 00000011 ts 2

11-19 12:27:22.956  16817-16847/delightex.androidTest W/Adreno-GSL <gsl_ldd_control:466>: ioctl fd 24 code 0xc02c093d (IOCTL_KGSL_SUBMIT_COMMANDS) failed: errno 35 Resource deadlock would occur

11-19 12:27:22.956  16817-16847/delightex.androidTest W/Adreno-GSL <log_gpu_snapshot:375>: panel.gpuSnapshotPath is not set.not generating user snapshot

  • Up0
  • Down0
pkirill
Join Date: 18 Nov 15
Posts: 5
Posted: Fri, 2015-11-20 15:44

this is the test to reproduce

https://drive.google.com/file/d/0BxT5Kv3pTStLVWJHMG9BcHh3ZFU/view

select ManAnimation test

  • Up0
  • Down0
mhfeldma Moderator
Join Date: 29 Nov 12
Posts: 310
Posted: Tue, 2015-11-24 15:04

Hi..  Thanks for providing the apk with an easy to reproduce example.

We've been able to duplicate the crash on Nexus 6 with the Android M build as you described.  The animations seem to be ok on previous L builds.  We'll need to involve our driver team to better analyze the logs.

 

  • Up0
  • Down0
pkirill
Join Date: 18 Nov 15
Posts: 5
Posted: Sat, 2015-11-28 11:49

Hi, please stay me informed with the progress

Thanks

 

 

  • Up0
  • Down0
or Register

Opinions expressed in the content posted here are the personal opinions of the original authors, and do not necessarily reflect those of Qualcomm Incorporated or its subsidiaries (“Qualcomm”). The content is provided for informational purposes only and is not meant to be an endorsement or representation by Qualcomm or any other party. This site may also provide links or references to non-Qualcomm sites and resources. Qualcomm makes no representations, warranties, or other commitments whatsoever about any non-Qualcomm sites or third-party resources that may be referenced, accessible from, or linked to this site.