I am trying to do a Process profiling using AMD's uProf. After stopping the process, the profiler gets stuck on "Processing Data..."
Anyone knows why this might be? Running latest version as of today
Can you provide more details about the OS, profiling type, profile configuration details? Was it a system wide profile? Was Callstack profiling enabled? What was the profiling duration?
Also check if the env var _NT_SYMBOL_PATH is set to any value?
Latest Windows 10, I am just using the default settings for the application and that doesn't work, I also tried other types of default profiles but still no luck. A system wide profile works. The profiling duration was 20 seconds, no callstacks, just default settings to profile a running app.
The PATH variable is set
I seriously don't understand what the issue is. The application runs fine when i start the profiling, with passed parameters i need for it.
But when it comes to Processing the data it just gets stuck doing it forever. It would be nice to get more information about the issue, or how long it has left until the analysis complete. Maybe i need to wait more than 10-20 minutes (before i give up) to complete the analysis? The recording is usually 1-2 minutes so not THAT long.
The CPU is idling, doesn't seem like it's doing anything too. Or the SSD...
Running on 188.8.131.52
Ok, it worked after a long waiting time.
I have the same problem.
I'm on Windows 10. I haven't set the _NT_SYMBOL_PATH variable and disabled the download symbols option.
It gets stuck in processing data and I give up and close it.
How long did it take you to work?
The next version release of uProf will be out very soon. The new version should fix the issue observed by you. Please try this on the coming version and let us know if that helps.
If the CPU is idling, it is most likely downloading the symbols from Microsoft Symbol Server, will you be able to try profiling with "Load symbols from Microsoft Symbol Server" option disabled and as well unsetting the _NT_SYMBOL_PATH variable ?
congrats on the new release!
With the message log console I was able to see if uprof was stuck and managed to locate the problem.
On windows and with Visual Studio, it seems that uprof works fine if we set the linker option to "FULL" but gets stuck in processing data if we have set the linker option to "FASTLINK". Thus, I switched to full link and works fine!!
Can you check if there is any problem with fastlink? It's also the default option in Visual Studio