Crash calling glDrawElements

This topic contains 1 reply, has 2 voices, and was last updated by  Joe Davis 5 years, 2 months ago.

Viewing 2 posts - 1 through 2 (of 2 total)
  • Author
    Posts
  • #30914

    kottle
    Member

    Hi all,
    after several tests on my devices I got a severe crash due to a specific PowerVR driver version(
     libGLESv1_CM_POWERVR_SGX530_125.so.1.1.16.3977bundled on LG P970 and LGP920), below the stack trace:

    07-02 14:28:54.557 15363 15384 V  glDrawElements 48930 4c626c60 17812 4c5c2060 
    07-02 14:28:54.564  1616  1616 I DEBUG   : *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** ***
    07-02 14:28:54.564  1616  1616 I DEBUG   : Build fingerprint: ‘lge/lge_bprj/lgp970/lgp970:2.2.2/FRG83G/LG-P970-V10a.41D00508:user/release-keys’
    07-02 14:28:54.564  1616  1616 I DEBUG   : pid: 15363, tid: 15384  >>> com.jeppesen.app <<<
    07-02 14:28:54.564  1616  1616 I DEBUG   : at : (2012-07-02 14:28:54.000570770 UTC) -2
    07-02 14:28:54.564  1616  1616 I DEBUG   : signal 11 (SIGSEGV), fault addr 00000000
    07-02 14:28:54.564  1616  1616 I DEBUG   :  r0 00000000  r1 4c5c20a0  r2 00022c20  r3 00000000
    07-02 14:28:54.564  1616  1616 I DEBUG   :  r4 002fa318  r5 002faf64  r6 00000000  r7 00004594
    07-02 14:28:54.564  1616  1616 I DEBUG   :  r8 00011654  r9 00000000  10 00000004  fp 00000000
    ……
    07-02 14:28:54.564  1616  1616 I DEBUG   :  d28 3f12e167458a3c56  d29 3f1460eac009f537
    07-02 14:28:54.564  1616  1616 I DEBUG   :  d30 3efb2a7074bf7ad4  d31 be10bd9798800000
    07-02 14:28:54.564  1616  1616 I DEBUG   :  scr 20000012
    07-02 14:28:54.564  1616  1616 I DEBUG   : 
    07-02 14:28:54.635  1616  1616 I DEBUG   :          #00  pc 0000f218  /system/lib/libc.so
    07-02 14:28:54.635  1616  1616 I DEBUG   :          #01  lr 83505f28  /system/lib/egl/libGLESv1_CM_POWERVR_SGX530_125.so.1.1.16.3977

    After several tests I found the issue is due to the call glDrawElements if the number of indices passed to the GPU is more than 17k limiting the number of vertices to 6k and the crash disappears.

    My questions are:

    1. Has someone experience on that kind of crash?
    2. Do you think that limiting the number of indices could solve the crash issue on the 95% of devices and also do you think this value can change at run time?
    Thanks,
    kottle

    #35988

    Joe Davis
    Member

    Hi,

    I’ve spoken to our driver team about this issue, but they are not familiar with this bug. Because of this, we cannot say for certain that the workaround will solve the problem on all devices. It’s possible that this bug is specific to this driver and newer drivers (e.g. 1.7>) may not have the same issue.

    Thanks,
    Joe

Viewing 2 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic.