Frustrating Build Issue

[Mark_Yedinak]

I am experiencing a very frustrating build issue with LV 2018. My application build keeps crashing and the log file contains the following after every crash:

<Bunch of generic stuff>

starting LabVIEW Execution System 14 Thread 0 , capacity: 24 at [3816363687.88565207, (15:01:27.885652066 2024:12:06)]
starting LabVIEW Execution System 14 Thread 1 , capacity: 24 at [3816363687.88565207, (15:01:27.885652066 2024:12:06)]
starting LabVIEW Execution System 14 Thread 2 , capacity: 24 at [3816363687.88565207, (15:01:27.885652066 2024:12:06)]
starting LabVIEW Execution System 14 Thread 3 , capacity: 24 at [3816363687.88565207, (15:01:27.885652066 2024:12:06)]
LINKOBJ_BROKEN: LinkObj w/ identity [LinkIdentity "Message Logging.lvlib:Formatted.lvclass" [ My Computer Build Context]
UDClassLibrary::SetSelfErrorsCORE - missing parent on [LinkIdentity "Message Logging.lvlib:Formatted.lvclass" [ My Computer Build Context]
parent is [LinkIdentity "Message Logging.lvlib:File System.lvclass" [ My Computer Build Context], flags are 16
mFlags=16930
VI_NOTBROKEN (3): [VI "Message Handler.lvlib:Message Handler.lvclass:Message Process Server.vi" (0x1dc43740)]
SetVIIdle on a previously viBad VI: vi=true
VI_NOTBROKEN (3): [VI "Message Handler.lvlib:Message Handler.lvclass:Start Process Server.vi" (0x1dc4ea00)]
SetVIIdle on a previously viBad VI: vi=true
VI_NOTBROKEN (3): [VI "Message Handler.lvlib:Message Handler.lvclass:Message Server.vi" (0x1dc4f450)]

<A whole bunch of similar error messages for different libraries/vis>

I have opened every single VI of every library/class listed in the log. None are broken VIs. The project containing the application that I am building shows no errors and the VI that is being built for the application runs fine in the development environment. I have cleared the compiled cache numerous times yet every build will still fail. This is quite frustrating. The builds had worked several times and then after very minor code changes the builds starting crashing every build. All code is marked as separate compiled code from source.

Any thoughts on how to resolve this issue?

[paul_a_cardinale]

1. Revert to the version before the "very minor code changes" then rebuild to confirm that LabVIEW has not been damaged.
2. Reimplement those code changes one at a time, rebuilding each time.
3. Take a close look at the change that results in the build crashing.

Other points:

• Don't have an uninitialized shift register that holds a class.
• If possible clear all class mutation histories.
• Watch out for certain combinations:
  • XNodes inside malleable VIs.
  • XNodes inside Express VIs.
  • Malleable VIs inside Express VIs.

[Mark_Yedinak]

Thanks for the suggestions.

Finally able to get back to looking at this issue again. I looked through what SCC was saying was modified and I found 3 VIs that were marked as changed that I did not update. It should be noted that all of the code is marked to separate compiled from source. I reverted those back and the build is working again. I can't wait to get off of LV 2018 but for the moment I am restricted to it due to some older machines running old Windows Server 2012. There is a plan to migrate to newer servers but that has not been completed yet.

In terms of your three bullet points, points 1 and 3 are a non-issue as they don't exist in the code. I haven't really checked about clearing the class mutation histories but will keep that in mind for the future.