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

[Hooovahh]

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.

[Darren]

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.

[D_mitriy]

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.

[D_mitriy · Accepted solution]

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

[altenbach]

---

@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.

[D_mitriy]

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

[altenbach]

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)

[D_mitriy]

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

[billko]

---

@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.

[hunter_jki]

I had a recent support request related to cache behavior. I requested NI document all of the undocumented features, and they obliged!

LabVIEW User Cache Value Remains Unchanged After Clearance

https://knowledge.ni.com/KnowledgeArticleDetails?id=kA0VU0000004OyD0AU&l=en-US