Hi,
When using Adreno Profiler 3.7 to analysis a OpenGL ES 3.0 workload named GFXBench 3.0, the app crash when start. Is that mean the profiler does not support OpenGL ES 3.0 API?
Hi,
When using Adreno Profiler 3.7 to analysis a OpenGL ES 3.0 workload named GFXBench 3.0, the app crash when start. Is that mean the profiler does not support OpenGL ES 3.0 API?
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.
Which device are you trying to use Profiler with?
Profiler does support OpenGL ES 3.0, but there could be device-side issues that are causing the crash.
We tried both Nexus5(Android 4.4.2) and Note3(N9008, Android 4.3), but both failed. Which device are you using?
We've tested GFX Bench on numerous devices and haven't had any issues with it. We just verified it again using both TRex and Manhattan on Nexus 5 with the factory image, and had no problems. Can you provide more details?
We also tested GFXBench3.0 on Nexus5 with factory image(KOT49H). We installed GFXBench3.0 from Google Play and the version is 3.0.11.
But when we start the app, the app creashes. The problem has somthing to do with signal 11 (SIGSEGV) on libGLESv2_adreno library. The detail debug information is attached.
Configuration summary:
Device: Nexus5 with factory image(KOT49H)
App: GFXBench 3.0.11
Details debug info:
Add Adreno Profiler version.
Configuration summary:
Device: Nexus5 with factory image(KOT49H)
App: GFXBench 3.0.11
Profiling tool: Adreno Profiler 3.7.5179.5103
Do you have any progress on this bug? Is it the problem of driver?
We've not been able to duplicate this problem. Can you try running the latest version of Profiler (3.8, released today) to see if you're still experiencing it?
Yes, you are right. After upgrading, it's now working on my nexus5. Thanks a lot for your help.