Forums - Profiler hangs when launching Vulkan application

4 posts / 0 new
Last post
Profiler hangs when launching Vulkan application
FelixK
Join Date: 6 Dec 17
Posts: 3
Posted: Mon, 2018-10-29 08:54

I'm trying to take a snapshot of a Vulkan application on an Android Device (OnePlus 5T - which is using the Adreno 540 GPU).

As specified in the User's Manual, I connect my device to the Snapdragon Profiler and start the application via the 'Launch Application' button in the Snapshot tab. After that, Android will launch the application and a window appears saying "Waiting for debugger to attach...". After a few seconds, the window disappears and then the Snapdragon Profiler hangs. 

It'll then show as "not responding" in windows and the device shows a black screen.

Even after waiting 5 minutes, nothing happens.

---

Additionally, after closing the application on my phone (after unsuccessfully trying to take a Snapshot via the Profiler) subsequent attempts to create a Vulkan Instance using (vkCreateInstance) will fail with VK_LAYER_NOT_PRESENT, even if I don't specify any layers in VkInstanceCreateInfo. This happens with or without the Snapdragon Profiler connected.

Only after restarting the phone I am able again to create a valid Vulkan Instance.

This led me to believe that I had to include an undocumented Vulkan layer in my applications lib folder to be able to take snapshots with the Snapdragon Profiler. However, after scouting through my local Snapdragon Profiler installation folder, I couldn't find such library/Vulkan layer.

---

I'm using Snapdragon Profiler v2018.2.0.10032018

  • Up0
  • Down0
FelixK
Join Date: 6 Dec 17
Posts: 3
Posted: Wed, 2018-10-31 06:07

Same happens with the Google Pixel (Adreno 530). Would be really nice if I can get support for this.

I'm currently *not* able to make a Vulkan capture using the Snapdragon Profiler and can therefore not fix graphical issues on devices that have Adreno GPUs.

 

Edit: I was able to get it to work on the Google Pixel after closing Android Studio

  • Up0
  • Down0
FelixK
Join Date: 6 Dec 17
Posts: 3
Posted: Wed, 2018-10-31 07:38

Tried again with the LG G5 which also uses a Adreno 530.

While launching the application works, the application gets killed by the Android Memory Killer Daemon as soon as I want to take a Snapshot.

  • Up0
  • Down0
eshaw Moderator
Join Date: 12 May 16
Location: San Diego
Posts: 133
Posted: Fri, 2018-11-02 16:58

Hi Felix,

Sorry to hear you're having problems.

As I think you've already discovered, Android Studio (and any other tool that uses the Android debugger interface) can interfere with Profiler since it uses the debugger interface to attach to a Vulkan process.

The problem with Profiler leaving the device in a bad state is something we plan address in a future release. The problem is that Profiler sets the debug.vulkan.layer.1 Android property to load profiling layer, but if that property doesn't get cleared when you run the app again it can't load the layer. So the workaround (fast that rebooting the device) is to clear that property using adb setprop.

We haven't seen the issue with the memory killer before. After attempting a snapshot, you can use the Submit Feedback item in Profiler's Help menu to gather logs from Profiler and the device. If you send us those logs we may be able to get more information about the problem.

Eric

 

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