LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

LabVIEW 2022 Q3 "clear compiled object cache" does not work as expected

Solved!
Go to solution

Oh boy.  Well thank you for giving some help on finding this.  Should I presume that NIPM is the only way to get this patch?  What about offline machines?  Do I need to be going and grabbing the NIPM package from the cached location?  I'm finding lots of disappointing cracks in NI's web and NIPM experience this morning.

0 Kudos
Message 11 of 19
(1,327 Views)

To my knowledge NIPM is the only way to get this patch, so yeah, more pain in grabbing the package from the cache. I agree that it's disappointing.

0 Kudos
Message 12 of 19
(1,323 Views)

Looks like that. And, by the way, I have this patch installed (according to NIPM), but the "clear compiled object cache" bug and icons bug are both present.

0 Kudos
Message 13 of 19
(1,319 Views)
Solution
Accepted by topic author D_mitriy

OK, I used workaround for that:

  • In the project properties to make sure that all objects has separated compiled code from VI (mark if necessary).
  • Then, project saved, LabVIEW closed, object cache removed manually from the LabVIEW data directory (\Documents\LabVIEW Data\VIObjCache and \Documents\LabVIEW Data\AppBuilderCache in my case).

After the manual cleaning LabVIEW correctly shows empty cache at first start. But this is somehwat unhandy I would say.

 

EDIT: one more cache found in \Program Files\National Instruments\LabVIEW 2022\VIObjCache

0 Kudos
Message 14 of 19
(1,250 Views)

@D_mitriy wrote:

EDIT: one more cache found in \Program Files\National Instruments\LabVIEW 2022\VIObjCache


Not sure why you would ever want to touch that, because it is probably quite static and just the compiled code of the system VIs.

0 Kudos
Message 15 of 19
(1,231 Views)

Well, it works and does the job without the bad consequences - why not?

0 Kudos
Message 16 of 19
(1,197 Views)

 

Clearing the compiled cache of the LabVIEW system has the "bad" consequence that every system VI needs to be recompiled, making the next loading probably quite slow. 😄

 

(depending on your settings, it might even compile with fewer optimizations)

0 Kudos
Message 17 of 19
(1,165 Views)

I see the point. Probably I should try to do that once again with the compiler optimizations maxed out 🙂

0 Kudos
Message 18 of 19
(1,150 Views)

@D_mitriy wrote:

I see the point. Probably I should try to do that once again with the compiler optimizations maxed out 🙂


I think I read somewhere that "over-optimization" might lead to unexpected results in certain situations, and it was probably best to use "standard" optimizations.  But that discussion was a LONG time ago and the situation may have changed with the advance of optimization techniques.

Bill
CLD
(Mid-Level minion.)
My support system ensures that I don't look totally incompetent.
Proud to say that I've progressed beyond knowing just enough to be dangerous. I now know enough to know that I have no clue about anything at all.
Humble author of the CLAD Nugget.
0 Kudos
Message 19 of 19
(1,131 Views)