VTune randomly failing on loading .trace files

[ejo]

Hi,

I'm using Intel(R) oneAPI VTune(TM) Profiler 2021.6.0 (build 618723) Command Line Tool to profile a Python 3.8.11 application, but vtune -collect hotspots randomly fails with:

vtune: Error: Cannot load data file `/path/to/vtune_hs/data.0/13748-13758.0.trace' (Cannot resolve managed part of the application. Please archive your project data and provide it to the Technical Support for further investigation.).

Any idea how I can solve that issue? 

The .trace file is attached.

Thank you!

[JaideepK_Intel]

Hi,

Thank you for posting in Intel Communities.

We are working on your issue internally and will get back to you with an update. can you try to upgrade your Vtune to the latest version and let us know if you are facing the same issue ?

Link: Download the Intel® VTune™ Profiler

>>If you continue to experience similar problems after upgrading Vtune, please share the details below.

1. OS details and processor details.

For windows:

1. Run command prompt as administrator

2. To set the environment variables run the below command:

<Vtune_installation_directory\2022.2.0\vtune-vars.bat>

example: C:\Program Files (x86)\Intel\oneAPI\vtune\2022.2.0\vtune-vars.bat

3. To run vtune-self-checker run the below command:

<Vtune_installation_directory\2022.2.0\bin64\vtune-self-checker.bat>

example: C:\Program Files (x86)\Intel\oneAPI\vtune\2022.3.0\bin64\vtune-self-checker.bat

For linux:

sh <oneapi_install_directory>/vtune/latest/bin64/vtune-self-checker.sh

(eg: sh /opt/intel/oneapi/vtune/latest/bin64/vtune-self-checker.sh)

Please attach the self-checker log (latest version of Vtune) to proceed further.

Thanks,

Jaideep

[ejo]

Dear Jaideep,
Thank you for the feedback.
Please find attached the log of the self-checker for the latest version of vtune.
The problem persists but it seems to be linked to Conda environments though. If I duplicate my Python environment using venv, vtune has no issue.

$ cat /etc/os-release
NAME="Red Hat Enterprise Linux Server"
VERSION="7.7 (Maipo)"
ID="rhel"
ID_LIKE="fedora"
VARIANT="Server"
VARIANT_ID="server"
VERSION_ID="7.7"

$ lscpu
Architecture: x86_64
CPU op-mode(s): 32-bit, 64-bit
Byte Order: Little Endian
CPU(s): 40
On-line CPU(s) list: 0-39
Thread(s) per core: 1
Core(s) per socket: 20
Socket(s): 2
NUMA node(s): 2
Vendor ID: GenuineIntel
CPU family: 6
Model: 85
Model name: Intel(R) Xeon(R) Gold 6230 CPU @ 2.10GHz
Stepping: 7
CPU MHz: 2799.444
CPU max MHz: 3900.0000
CPU min MHz: 800.0000
BogoMIPS: 4200.00
Virtualization: VT-x
L1d cache: 32K
L1i cache: 32K
L2 cache: 1024K
L3 cache: 28160K
NUMA node0 CPU(s): 0-19
NUMA node1 CPU(s): 20-39
Flags: fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx pdpe1gb rdtscp lm constant_tsc art arch_perfmon pebs bts rep_good nopl xtopology nonstop_tsc aperfmperf eagerfpu pni pclmulqdq dtes64 monitor ds_cpl vmx smx est tm2 ssse3 sdbg fma cx16 xtpr pdcm pcid dca sse4_1 sse4_2 x2apic movbe popcnt tsc_deadline_timer aes xsave avx f16c rdrand lahf_lm abm 3dnowprefetch epb cat_l3 cdp_l3 invpcid_single intel_ppin intel_pt ssbd mba ibrs ibpb stibp ibrs_enhanced tpr_shadow vnmi flexpriority ept vpid fsgsbase tsc_adjust bmi1 hle avx2 smep bmi2 erms invpcid rtm cqm mpx rdt_a avx512f avx512dq rdseed adx smap clflushopt clwb avx512cd avx512bw avx512vl xsaveopt xsavec xgetbv1 cqm_llc cqm_occup_llc cqm_mbm_total cqm_mbm_local dtherm ida arat pln pts hwp hwp_act_window hwp_pkg_req pku ospke avx512_vnni md_clear spec_ctrl intel_stibp flush_l1d arch_capabilities

[JaideepK_Intel]

Hi,

Glad that you tried on another duplicate environment. The old conda environment might have some missing dependencies, hence, Vtune is throwing an error. You can continue working on duplicate environment as you mentioned that Vtune is working fine in it.

As your issue is resolved, can we discontinue monitoring this thread ?

Thanks,

Jaideep

[JaideepK_Intel]

Hi,

If this resolves your issue, make sure to accept this as a solution. This would help others with similar issue. Thank you!

Regards,

Jaideep

[JaideepK_Intel]

Hi,

We assume that your issue is resolved. If you need any additional information, please post a new question as this thread will no longer be monitored by Intel.

Thanks,

Jaideep