Here is a list of known issues.
On a Windows system with Microsoft Visual Studio versions 2019 or 2022 installed, and on which Microsoft Visual C++ redistributable package was uninstalled for any reason:
AMD uProf installation may not detect that the redistributable package is missing and thus fails to install the requisite redistributable package.
We recommend you verify or initiate installation of the Microsoft Visual C++ redistributable package before installing AMD uProf on a Windows system.
If the installer doesn’t have permission to access required location for installation and it cannot write to system directories or registry keys, installation may not complete.
On Linux, while upgrading AMD uProf using RPM package installer, the upgrade process might leave some folders of the previous version in the /opt/AMDuProf_<old version> directory. These files or folders from the previous version will have no impact on the upgraded version of AMD uProf.
Some samples may be missed when performing a combined PMC and Timer-based sampling profile run.
If AMD uProf is installed in a path that includes non-ASCII Unicode characters, profiling does not work.
The CPU Profiler does not support profiling of a Windows Store app.
The CPU Profiler report command invocation with --symbol-server and --symbol-cache-diroptions may crash if Ctrl-C is pressed.
Unsupported instructions such as, VDPBF16PS are shown as BAD DASM in IMIX and Source view.
Occasionally, core PMC samples may not be collected while profiling on KVM guest environment.
On an ESXi guest environment, a high number of samples are collected in comparison to the same application running on a bare-metal system.
Custom profiling with IBS and TBP or EBP events might show zero or fewer samples in the report. To overcome this issue, do not combine - IBS with the other profiling events (TBP or EBP) during the custom profiling.
libclang-cpp.so library bundled with AOCC 3.2 is not CXX11 ABI compliant. AMD uProf OS tracing functionality depends on libclang library (with abi cxx11 support). While running applications compiled with AOCC 3.2, the LD_LIBRARY_PATH points to AOCC 3.2 bin/lib paths and hence, AMD uProf fails giving an undefined symbols error. This issue is not observed if LD_LIBRARY_PATH is not set to AOCC 3.2 libs.
For Java applications running for a long time (more than an hour), the sample data attributed to Java methods might not be accurate.
IBS and MPI profiling are not recommended to be run concurrently as a very large dataset will accumulate.
GUI may crash when the thread timeline option is selected for importing a session using the option –category cpu.
The data volume shown in an MPI report is not evenly distributed among all the ranks involved for the MPI APIs performing more than one communication operation. For example, MPI_SendRecv, MPI_Waitall, and so on, due to which, the MPI report might not match with other MPI tracing tools evenly distributing the volume
If the profiled system enters Sleep or Hibernate mode during a Live Power Profiling session, only the data collected before hibernation will be displayed, and the navigation slider will become unresponsive.
Energy analysis is not supported.
Collecting multiple groups of Core PMC based metrics across all the cores in root mode may result in reduced accuracy of the collected data.
All virtual machine (VM) configurations have not been tested.
On Windows, the Roofline model may display incorrect bandwidth data for certain applications.
Use the --metrics option to collect custom perfCtl based metrics provided in the command line. MSR based events (aperf, mperf, irperf, and tsc) are not allowed to collect without at least one valid PMC event in the given metrics. In such a case, behavior will be undefined.
While using the --use-linux-perf flag, you cannot use the options -C and -p together in Linux.
All VM configurations have not been tested.
Sporadically we get “Failed to Configure CountMode API” error while collecting multiple metrics together.
On RHEL9.6, combining OS-Tracing with Time Based profile is not supported.
CSV report shows incorrect “Total Time” for Recursive function Tracing.
Memory trace on Linux kernel version 6.14.0-36 is not supported.
For DiskIO, some devices appear as “unknown” device in csv report.
Behavior of Domain Task API along with Profile control API is not deterministic
ITT report generation crashes in case we have “ ,”(comma) in domain name
Importing only GPU traces is not supported.
AMDuProf crashes when a timer event is selected through the filter option in the Custom configuration page.
For python profiling, call stack information may be inaccurate if frame pointers are not enabled in profiled application.