Forums - Snapshot crash with OnePlus 5T

4 posts / 0 new
Last post
Snapshot crash with OnePlus 5T
sebastian_bugiu
Join Date: 18 Nov 16
Posts: 2
Posted: Sun, 2018-03-11 14:32

I was trying to profile an OpenGL application using Snapdragon Profiler 2.2.0 from Dec 15 2017 on a OnePlus 5T and whenever I create a snapshot for my application it crashes, on both Windows and Linux. The good thing is that I got the stacktrace for Linux, you can find it here: https://drive.google.com/open?id=1w-dnKMlsKVCJZ3ZJWY96QZs42n_dL0Qu

Additional info that might help: The game that I am profiling is using lots of textures and on Adreno Profiler with a Nexus 5 it took about 2 minutes for a capture frame to finish, but it worked in the end. Also, realtime information and traces seem to work, but I need the snapshot functionality to debug some shader issues.

I am using the following permissions:

<uses-permission android:name="android.permission.INTERNET" />
<uses-permission android:name="android.permission.ACCESS_NETWORK_STATE" />
<uses-permission android:name="android.permission.WRITE_EXTERNAL_STORAGE" />
<uses-permission android:name="android.permission.READ_EXTERNAL_STORAGE" />
<uses-permission android:name="android.permission.WAKE_LOCK" />
<uses-permission android:name="com.qti.permission.PROFILER" />

<uses-feature android:glEsVersion="0x00030000" android:required="true" />

I have also tested on a Nokia 5 and there it also crashed with application not responding, but it took much longer. During around 2 minutes the application stopped running on the phone, but after that it resumed. It seemed that it started downloading the data but then it just remained there for another 10 minutes unresponsive (on the PC). After that, I decided to close it and got the not responding menu. This happened on both Windows and Ubuntu 16.04.

If you need more info, don't hesitate to ask.

  • Up0
  • Down0
Carlos Dominguez Moderator
Join Date: 27 Jul 15
Location: San Diego
Posts: 110
Posted: Tue, 2018-03-13 09:43

Could you compress the session folder located in 'Documents/SnapdragonProfiler/[date_of_session]' and share it either here or through PM please? My initial hunch is that the crash may be related with texture formats but having the SDP session will help clarify that and will help us debug your issue. 

  • Up0
  • Down0
sebastian_bugiu
Join Date: 18 Nov 16
Posts: 2
Posted: Tue, 2018-03-13 12:17

The data has been zipped here: https://drive.google.com/open?id=1YKle5nZO88Cvf8qNhQ-kDaHkPQGwp2yz

It could be something related to texture formats because I don't see some of the objects rendered on the screen. All the textured ships from the game are practically invisible, but the menus and heads up display are visible (another set of textures). Also, I've noticed that on Nexus 5 I see the textured ships but the textures were reversed: ABGR vs ARGB. That was most probably a bug in the engine that I am using but after I've corrected this and used Adreno Profiler again, I've noticed that the textures loaded by the profiler were incorrect. For example Adreno Profiler would report completely green textures for the first 4-5 mipmaps, but they were correct after that. It looked like a driver bug, but maybe there was something wrong with Adreno Profiler also? So I bought a OnePlus 5T and downloaded Snapdragon Profiler in order to nail it down...

I forgot to mention I am not getting any GL errors. All GL calls are checked for errors in the debug build and there are none.

Anything more I can do to help you, please ask! If you want, I can PM you the apk that is causing the problem. Hopefully it will not crash before starting. It's still under heavy development :)

  • Up0
  • Down0
Carlos Dominguez Moderator
Join Date: 27 Jul 15
Location: San Diego
Posts: 110
Posted: Tue, 2018-03-13 15:17

Thanks for the quick reply! We will look into your issue as soon as possible and update you once we have more information about it.

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