Execution Profiler: unexpected fatal error

[Wolfgang]

Hello,

in order to analyze the effect of multithreading (using pragma omp parallel) I enabled execution profiling in the Build options and added the call

CVIProfSetCurrentThreadProfiling(1);

as first line in the function of interest.

When running the (64 bit) debug version of the software (built with CVI 2019) I receive the following error from this call:

Library function error (return value == -5 [0xfffffffffffffffb]). An unexpected fatal error occurred in the Execution Profiler.
What should I do with this information?

What I can add:

without the line CVIProfSetCurrentThreadProfiling(1); after finishing my code resource tracking does not report any memory leak, however, when profiling is enabled (otherwise everything identical), I do get 5 warnings....

The three sample programs in the profiler directory work well so that I fear that it might be due to a non-compatibility of OpenMP with execution profiling...?

Help is much appreciated, thanks,

Wolfgang

[Wolfgang]

so far I was unable to narrow down the problem - no effect of OpenMP could be proved so my question remains what reason could cause this error...:

An unexpected fatal error occurred in the Execution Profiler

Thanks!

[Wolfgang]

My current understanding is that the problem of the execution profiler is caused by larger projects. I have tried different include files and build options with no effect observed, the demo programs also work as expected, but my two larger projects both cause the fatal error reported.

With this in my mind I was searching for the *.cvip file to see if my assumption could be correct, i.e., if the profiler file grows with the size of the project. Unfortunately, I could not find any of these files... Are they hidden, is the file extension other than documented,...?

[MelanieE]

Hi Wolfgang,

can you provide some code so I can try to reproduce this issue and have a deeper look into it?

Best,

Melanie

[Wolfgang]

Hi Melanie,

NI's local support stuff had reported this to NI US and told me that the bug has been reproduced and is going to be fixed:

"Der Stand ist aktuell, dass die NI Entwicklung bereits auf Ihren Forums Post intern reagiert haben und das von Ihnen beschriebe Verhakten als BUG identifiziert, der aktuell gefixt wird und voraussichtlich dieses Jahr noch in einem Patch für den CVI Execution Profiler 1.1 behoben werden soll."

Of course, I can provide a sample project via private mail / ftp, if useful.

Many thanks for addressing the issues

[MelanieE]

Hi Wolfgang,

thank you for the update. I guess this post wasn't linked to the local request. Since R&D is already working on this there is nothing else to do but wait for the fix at the moment.

I'll mark your post as the solution.

Best,

Melanie

[Wolfgang]

Version 1.1.1 of the execution profiler seems to fix this problem, thanks!

[Hosmer]

Version 1.1.1 does not install on Windows 10 systems with CVI 19.0.0 !!!!

[Wolfgang]

It does, I used NI Package Manager to update the software.

[Hosmer]

Yeah, that's exactly what I did. Package manager responds with a useless error message.

Are you also using CVI version 19.0.0 (49155) on Windows 10?