Forums - Warnings by Adreno-GSL, then app just suddenly dies (no crash log)

3 posts / 0 new
Last post
Warnings by Adreno-GSL, then app just suddenly dies (no crash log)
xtrawurst
Join Date: 19 Jun 12
Posts: 4
Posted: Wed, 2016-10-19 15:01

We are experiencing some extremely odd behavior running our app on the Snapdragon 652 (Adreno 510):

At some (reproducible) point of usage of our app (after loading a 3D scene and creating many GL buffers and textures) the app just dies out of the blue without leaving a message on the log. There don't seem to be any Unix Signals involved. The app just dies. The only thing we get are some cryptic log warnings by Adreno-GSL right before the app exits:

10-20 03:03:59.126: W/Adreno-GSL(20487): <gsl_ldd_control:475>: ioctl fd 24 code 0x400c0907 (IOCTL_KGSL_DEVICE_WAITTIMESTAMP_CTXTID) failed: errno 35 Resource deadlock would occur

10-20 03:03:59.126: W/Adreno-GSL(20487): <log_gpu_snapshot:384>: panel.gpuSnapshotPath is not set.not generating user snapshot

10-20 03:03:59.126: W/Adreno-GSL(20487): <gsl_ldd_control:475>: ioctl fd 24 code 0xc0140933 (IOCTL_KGSL_TIMESTAMP_EVENT) failed: errno 22 Invalid argument

10-20 03:03:59.126: W/Adreno-GSL(20487): <ioctl_kgsl_syncobj_create:2979>: (19, 10, 6336) fail 22 Invalid argument

10-20 03:03:59.148: W/Adreno-GSL(20487): <gsl_ldd_control:475>: ioctl fd 24 code 0xc040094a (IOCTL_KGSL_GPU_COMMAND) failed: errno 35 Resource deadlock would occur

10-20 03:03:59.148: W/Adreno-GSL(20487): <log_gpu_snapshot:384>: panel.gpuSnapshotPath is not set.not generating user snapshot

10-20 03:03:59.149: W/Adreno-GSL(20487): <gsl_ldd_control:475>: ioctl fd 24 code 0xc040094a (IOCTL_KGSL_GPU_COMMAND) failed: errno 35 Resource deadlock would occur

10-20 03:03:59.149: W/Adreno-GSL(20487): <log_gpu_snapshot:384>: panel.gpuSnapshotPath is not set.not generating user snapshot

10-20 03:03:59.566: I/MSM-irqbalance(648): Decided to move IRQ51 from CPU2 to CPU3

10-20 03:03:59.750: I/WindowState(7174): WIN DEATH: Window{b69556c u0 SurfaceView}

10-20 03:03:59.752: D/GraphicsStats(7174): Buffer count: 3

10-20 03:03:59.768: I/WindowState(7174): WIN DEATH: Window{6946b2f u0 de.dotproduct/de.dotproduct.PurpleRayActivity}

10-20 03:03:59.974: I/ActivityManager(7174): Process de.dotproduct (pid 20487) has died

 

We are running into this issue on two separate devices (which have the same Snapdragon 652 chip):

1. Samsung Galaxy Tab S2 (T813)

2. Levovo Phab 2 Pro

We have already tried *lots* of debugging on this issue (including Address Sanitizer and other memory tools) but still can't find any issue in our app. There are no OpenGL errors either that would give us a hint on what's the problem.

Interestingly the issue hides when inserting logs at particular places in the code or commenting-out unrelated parts of the code. But, as I said, we've already thrown all kinds of memory and threading debugging at this to no avail. The issue also does not show up when loading other datasets (such as much larger scenes). We have some very experienced and seasoned engineers working on this but so far nobody has a clue about what's going on.

Also our app runs just fine on devices with other chips.

We would extremely appreciate any help finding this issue or at least helping us understand what Adreno-GSL is trying to tell us right before the app dies. Let me also add that we can almost always resolve crashes and instabilities in our app internally through our engineers' experience in (graphics) development and debugging. However in this case we're all clueless and I would not be posting this on this forum if we weren't desperate for answers...

  • Up0
  • Down0
florian.komposch
Join Date: 6 Jun 20
Posts: 2
Posted: Sat, 2020-06-06 05:42

hey, i have literally the same issue, just in an other environment(Adreno 540).

I am using vulkan, and a minor texture gl copy part.

The application runs fine the first frames - till the W/Adreno-GSL warnings pop and and then the GPU seems to fail as the commited vulkan graphic and/or comute queues will crash, and wont releases fences we are waiting for.
 

Did you somehow solve or track this issue ?

 

 

 

 

  • Up0
  • Down0
florian.komposch
Join Date: 6 Jun 20
Posts: 2
Posted: Sat, 2020-06-06 05:43

hey, i have literally the same issue, just in an other environment(Adreno 540).

I am using vulkan, and a minor texture gl copy part.

The application runs fine the first frames - till the W/Adreno-GSL warnings pop and and then the GPU seems to fail as the commited vulkan graphic and/or comute queues will crash, and wont releases fences we are waiting for.
 

Did you somehow solve or track this issue ?

 

 

 

 

  • 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.