LV 2024 Q1 hard crash when opening VI

[Fedor]

I have been running into a very annoying and strange LV 2024 Q1 behavior - when I try to open a particular top-level VI LabVIEW  would hard crash without any trace or error message. If I copy/paste the same VI into same folder with a new name or copy it to a different folder, it's opens ok, but after a few days it starts to crash again. LV would also crash if I try to open VI programmatically via scripting. I tried clearing LV cache a few times to no avail. I am also using Git it it is possible that it first started happening after one of the pulls. I checked the behavior on another PC with LV 2024 Q1, and it started happening there too after a while. 

I cannot post the LV project here, and it may be unnecessary anyway since renaming/moving the VI fixes the problem for a while. 

I'd appreciate any help.

[Kyle97330]

Assuming you're running Windows, have you checked for crash logs even if there's no popup crash message?

There are 2 places you can look.

One is the Windows Event Viewer.  Open it, and under "Windows Logs -> Application", look for events with a "Level" of "Error" that occur with a timestamp close to the crash time.

The other is the LabVIEW crash reports folder.  Open Explorer, head to:

<User documents>\LabVIEW Data\LVInternalReports\

Do a search for any files generated in the subdirectories under that folder around the time of your crash.  If you can find either a "lvlog.txt" file, or a zip file that contains a "lvlog.txt" file, open that up.

It is possible that one of those two locations will direct you towards a more specific cause, such as a certain DLL or internal LabVIEW warning/error.

[Fedor]

Thank you for the suggestion. It seems that errors are related to cache corruption.

I conducted a few experiments and I observed some puzzling behavior. I have A.vi and B.vi. If I take the following steps: 1. Clear compiled VI cache. 2. open A.vi then it opens OK. If I try to open B.vi  next, it crashes LabVIEW. I can still open A.vi after crash. It does not matter if A.vi is open or closed during the attempt to load B.vi, it will crash the LabVIEW.

Then if I clear cache again, I can open B.vi. If I then try to open A.vi it crashes LabVIEW. I can still open B.vi afterward. 

How can I fix my LabVIEW 2024 Q1 install?

[raphschru]

Maybe your code became corrupted for some reason...

With Git, can you revert to a version that did not crash?

Or what if you recode your VIs "A.vi" and "B.vi" from scratch (manually, without copying)?

---

@Fedor wrote:

I cannot post the LV project here, and it may be unnecessary anyway since renaming/moving the VI fixes the problem for a while. 

---

Can you at least post VIs "A.vi" and "B.vi"?

I only have up to LV2023, so if you could save it for version 23.0 (hoping you manage to do it without crashing and if it works, that it won't eliminate the corruption for us to analyze).

Otherwise, how does your block diagram / front panel look like?

Just enumerating what I know can crash LabVIEW:

 - Do you have a very large diagram, elements placed very far away or deeply nested structures, ...?

 - Do you have very large constants or controls that go out of screen?

 - Are you using special objects like XControls or XNodes?

 - Are you using Timed Loops?

 - Are you using class property nodes?

 - Are you using malleable VIs, or generic VIs?

 - Have you made some "experimental" VI Scripting manipulations on these VIs?

...

Regards,

Raphaël.

[thols]

I would: mass compile and check for bad VIs and fix those. If that does not help, force-recompile and then mass-compile again.

[Fedor]

I don't have any of the issues that you have listed. I think it's just a bug in LV 2024.1. Perhaps it's time to upgrade and see see if the bug goes away. 

I have another bug that periodically pops up during application build, the dreaded untraceable 'broken diagram in Actor.vi'. I think that the two bugs might be related because I can work around the later one by also clearing the cache in a particular order.