VTune crash on Linux Console App

SeeRich · ‎04-22-2023

I am attempting to profile an application on Ubuntu 22.04 using VTune Profiler (GUI).

Error:

Assertion failed: tool:1353: g_instr_global.is_libpthread_so_initialized == 0 : g_instr_global.is_libpthread_so_initialized == 1 . Please contact the technical support.

Setup details:

VTune Profiler 2023.1.0, Hotspots Algorithm, User-Mode Sampling

Ubuntu 22.04

Application details:

ffmpeg -y -f lavfi -i testsrc=duration=3600:size=1280x720:rate=30 testsrc.mp4

This command should create a 10-minute MP4 test video.

Verbose details:

In the VTune GUI when I try "Launch Application", VTune doesn't report an error but instead immediately finishes as if the application arguments weren't passed and the application didn't actually run.
When I try "Attach to Process", that is when I encounter the error.

ThasneemV_Intel · ‎04-25-2023

Hi,

Thanks for posting in Intel Communities.

We assume that you are performing the analysis as illustrated in the below screenshot:

If ffmpeg is installed using apt, then it would be installed into /usr/bin/ directory as given below:

user@hostname:~$ ls /usr/bin/ | grep ffmpeg
ffmpeg

When you try to profile an application via launch application option, by default the output will be stored in the directory where the application exists. This can be disabled by unticking the "Use application directory as working directory" option and choosing the location where proper write permission is available (e.g.: your home directory) as illustrated below:

Regarding your second issue, we tried profiling the ffmpeg application using attach to process method as suggested by you, but it was failing with the error that you mentioned. But the sample matrix application does not have any issues when profiling using attach to process method. The issue only occurs for ffmpeg. We are investigating the same with the internal team and will let you know the updates shortly.

Thanks,

Thasneem Vazim

ThasneemV_Intel · ‎05-02-2023

Hi,

Regarding your second issue, we kindly suggest you run the following code in your system where you have seen the issue and share the output with us:

#ifdef __INTEL_LLVM_COMPILER 

  printf("Intel icx %d %s\n", _INTEL_LLVM_COMPILER, __VERSION_); 

#else 

#ifdef __INTEL_COMPILER 

  printf("Intel icc %d.%d (%d)\n", _INTEL_COMPILER, __INTEL_COMPILER_UPDATE,  _INTEL_COMPILER_BUILD_DATE); 

#else 

  printf("GNU gcc %d.%d.%d\n", _GNUC, __GNUC_MINOR, __GNUC_PATCHLEVEL_); 

#endif 

#endif 

  printf("GNU LIBC version: %d.%d; %s\n", _GLIBC, __GLIBC_MINOR_, gnu_get_libc_version());

Meanwhile, we have tried hardware event-based sampling on the same infrastructure as yours and we didn’t observe the “Assertion failed” error. We got the required results with Hardware event based sampling.

Below are the steps to do the same:

For hardware event based sampling, we need to run vtune as administrator:

sudo su

Run hotspot analysis on vtune:

vtune -collect hotspots -knob sampling-mode=hw -knob sampling-interval=0.5 -target-pid <ffmpeg pid>

Please try the above steps and let us know if the issue persists or not. If this resolves your issue, make sure to accept this as a solution. This would help others with a similar issue. Thank you!

Regards,

Thasneem Vazim

ThasneemV_Intel · ‎05-09-2023

Hi,

We have not heard back from you. If your issue is resolved, make sure to accept it as a solution. This would help others with similar issues.

Regards,

Thasneem Vazim

ThasneemV_Intel · ‎05-16-2023

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.

Regards,

Thasneem Vazim