Unable to profile code with VTune @ Linux: Insufficient memory

[mabalenk]

I need your help please. I'm struggling to profile my C/C++ code with Intel VTune v2025.1 on a RedHat Linux 8.10. The code is compiled with a GNU C++ compiler 12.10 and a "-g" flag. I can successfully run the "performance snapshot" analysis, but none of the "hotspots", "memory-access", "hpc-performance" or "threading". I use a command line interface to launch a profiling session. My profiling command is:

 /opt/intel/oneapi/vtune/latest/bin64/vtune -collect performance-snapshot -r <results_dir>/performance-snapshot <executable> <arguments>

My "hotspots" (and other) analyses crash at the final stage with an "insufficient memory" error:

vtune: Collection stopped.
vtune: Using result path `/hotspots'
vtune: Executing actions 19 % Resolving information for `libOpenVolumeMesh.so.1
vtune: Warning: Cannot locate debugging information for file `/lib64/libm.so.6'.
vtune: Executing actions 19 % Resolving information for `libiomp5.so'
vtune: Warning: Cannot locate debugging information for file `/lib/libiomp5.so'.
vtune: Executing actions 20 % Resolving information for `libmkl_rt.so.2'
vtune: Warning: Cannot locate debugging information for file `/lib/libmkl_rt.so.2'.
vtune: Warning: Cannot locate debugging information for file `/lib/libmkl_intel_lp64.so.2'.
vtune: Executing actions 20 % Resolving information for `libstdc++.so.6'
vtune: Warning: Cannot locate debugging information for file `/lib/libmkl_intel_thread.so.2'.
vtune: Executing actions 20 % Resolving information for `bash'
vtune: Warning: Cannot locate debugging information for file `/usr/bin/bash'.
vtune: Executing actions 20 % Resolving information for `libmkl_avx512.so.2'
vtune: Warning: Cannot locate debugging information for file `/usr/bin/dirname'.
vtune: Executing actions 21 % Resolving information for `libpthread.so.0'
vtune: Warning: Cannot locate debugging information for file `/lib64/libpthread.so.0'.
vtune: Executing actions 21 % Resolving information for `libdl.so.2'
vtune: Warning: Cannot locate debugging information for file `/lib64/libdl.so.2'.
vtune: Executing actions 21 % Resolving information for `libemthreadpool.so'
vtune: Warning: Cannot locate debugging information for file `/usr/bin/readlink'.
vtune: Executing actions 21 % Resolving information for `which'
vtune: Warning: Cannot locate debugging information for file `/usr/bin/which'.
vtune: Executing actions 21 % Resolving information for `libc.so.6'
vtune: Warning: Cannot locate debugging information for file `/lib64/libc.so.6'.
vtune: Executing actions 21 % Resolving information for `rm'
vtune: Warning: Cannot locate debugging information for file `/lib/libmkl_avx512.so.2'.
vtune: Warning: Cannot locate debugging information for file `/usr/bin/rm'.
vtune: Executing actions 22 % Resolving information for `libittnotify_collector
vtune: Warning: Cannot locate debugging information for file `/opt/intel/oneapi/vtune/2025.1/lib64/runtime/libittnotify_collector.so'.
vtune: Executing actions 22 % Resolving information for `libtpsstool.so'
vtune: Warning: Cannot locate debugging information for file `/opt/intel/oneapi/vtune/2025.1/lib64/libtpsstool.so'.
vtune: Executing actions 50 % done
vtune: Error: 0x40000002 (Insufficient memory)

I tried running this analysis on a machine with 2 TB of RAM and the VTune error was still the same. I can not believe VTune needs this much memory to finalise the result.

The Intel sampling driver is installed and loaded. I ran the vtune-self-checker.sh script and all types of analyses reported "O.K." status. Would you please help me to resolve this issue?

[mabalenk]

My CPU is Intel Xeon W-2223 CPU @ 3.60GHz and I have 64 GB of RAM and 32 GB of swap space. I can not upgrade VTune to 2025.5 because it won't recognise my CPU anymore.

[IvanChepiga]

There was an issue with profiling Python executables, caused the same Error type at finalization stage. If type of your executable is Python, please try to update VTune to the latest release.

[IvanChepiga]

Oh yes, I see you cannot upgrade VTune. If type of your executable is Python, please share details like version and distribution, will see if there is possible workaround.