Hi,
I was lucky to be able to use the profiler few days when I needed in the past, but now each time I made a try I am not able to use it. At least from the version 1.4 all versions crash a some points (connection to device, when capturing, when it compute the app list,...). I just can't use it any more with any device. I mostly use my Motorola Nexus 6 that run actually on Android 7.0.
I discover that the tegra nsight can run better for this device, that seems curious due to the hardware branding of the Nexus 6.
It is frustrating as I already saw some great features of the profiler, and now it take much more time for me to improve performances and realibility of our application for your hardware.
At least instead of crashes if there is compatibility issue with devices I am expecting proper feedback that can help me to solve that. Else I just want to give up.
You must see this post as a message of encouragements to do better.
Thank you for read.
PS: Original post in wrong sub-forum, so I moved it
I'm sorry you experienced difficulties using Adreno Profiler. This tool has been deprecated for some time now and is only recommended for profiling devices with Adreno A3XX family GPU's and below. I would encourage you to please try our newest Snapdragon Profiler which includes all the previous Adreno Profiler functionality and more data gathered from across the full system on a chip.
If your focus is on GPU profiling you will find that Snapdragon Profiler's 'Rendering Stages' trace metric is an invaluable tool to measure accurate GPU execution and to understand how the Adreno GPU is processing your frame on the various stages of our tiling architecture.
Sorry my mistake I post in the wrong sub forum, I am using snapdragon profiler obviously.
I had uninstall the adreno profiler since many months.
I move this thread in the right sub-forum (to Snapdragon profiler).
Sorry to hear you've been having problems. For starters, please try our new release (v1.6) if you haven't already as we made a number of stability fixes for that release. If you're still having issues with that version, please let us know some more specifics about your issues (what OS you are running the Profiler client on, what actions you are taking, etc.).
Eric
Yes I tried the version 1.6.
I am running it on Windows 10 64bits, and it crash when it scan the applications on the device, after discoring few applications (4 - 5) it crash. It is the same if I launch the profiling view.
OK, after it crashes if you open the Windows Event Viewer and go to Windows Logs -> Application, you should see an error log for .NET Runtime. In that log the first line should indicate that the application is SnapdragonProfiler.exe. If you can post the contents of that log it should tell us more about the problem.
Eric
Back with log that I get at home:
We've been able to reproduce your issue, and we believe it is caused by the regional formatting setting on your PC. Any format setting that uses a character other than period (.) for the decimal symbol causes an exception leading to the crash. We should have a fix implemented in the next release of Profiler, but in the mean time you can work around the issue by changing your formatting setting. This can be done via Control Panel -> Clock, Language, and Region -> Change the date, time or number format. You can either change the format selection at the top to English (United States), or you can click Additional settings... at the bottom and then change the decimal symbol to period (.). We understand this is not ideal since it is a system-wide setting, but it should allow you to use Profiler until the fix is available.
Eric
Hi,
The workaround works fine, but effectively it is not ideal as I need to let my computer in french to develop our application for PC and changing this settings is not easy because the country search is not possible in a really long list.
To avoid issues with the local a simple way is to force the C one on application startup with setlocale(LC_ALL, "C"); in c++. We use this on our application to have a fixed parsing of the application data files that isn't affected by the local settings of the user.
I hope to see the two fixes in a new version soon.
Thank you a lot for helps.