Reentrancy bug in LabVIEW 2024 Q3 with backsaving

[Nate@UT]

Thanks.  Filed new Service Request 03364720 echoing the behavior reported in this thread. 

[avogadro5]

---

Nate@UT wrote:

I've downloaded the OP's example project and confirmed that the described behavior is the exact same as the one I've been struggling with (I used 2023 files and 2024 app). 

No need to file a redundant bug report or post different code.  Rather, I'd just like see NI provide a fix for it ASAP... is there any way to "upvote" on the existing bug report?

---

NI is really opaque about this stuff, I didn't get a link to an issue page or a fix date or anything, just the number. And if I hadn't chosen to post it, you wouldn't know it was a confirmed bug.

[Yamaeda]

Maybe i misread/misunderstood, but is it the same behaviour if you do a manual "save for previous" or just the automatic version?

[Nate@UT]

I have confirmed that the bug happens if both cases if you either:

a) create a reentrant VI in LV2024 and then manually back-save to a v2023 file, or

b) open a reentrant VI which was originally created and saved in LV2023 and run it in LV2024.

The issue happens when you've modified and saved the 2023 reentrant VI from within LV 2024 editor, but haven't yet closed the project and reopened it.  If you open the project without making modifications in the reentrant VI, the behavior is correct.  But that correct behavior disappears as soon as any modification is made and the VI is re-saved. 

[Quiztus2]

It also happens when opening 23 code in the 24 IDE and doing a mass compile. I didn't touch anything before mass compile.