LabVIEW 2018 crashes a lot!

[10Degree]

Anyone else having crash issues with LV 2018?  I have been using LV since 2005 and I have never had LV crash problems like this.

We run 32-bit LV.  Crashes at times seem related to the use of a particular VI (such as the File Dialog express vi), and other times just systematic crash death.  It will work in the design environment and crash in a compiled EXE at some times, and crash in the design environment at other times.  We have tried uninstalling and re-installing LV and this has not worked.  Multiple users on multiple machines experience problems.  We have tried re-building from scratch vi's that seem to crash and this doesn't always fix the problems.  Any thoughts?  Any 2018 updates?  If I could go back to 2017 I would.

[JÞB]

2018 is pretty stable.  Which makes me wonder how stable your code base is.  Did you follow the upgrade instructions?  What unit test changes occurred during upgrade?  Were any warnings thrown by the mass compile process?

Or, did you just install a new version delete the old IDE and wing it?

[10Degree]

We have always been pretty careful during a LabVIEW upgrade process.  Like I said, I have been doing this since LV 7 without experiencing the type of instability I experience with 2018.  The "wing it" comment was funny.  A little cynical and uncalled for, but funny.

[JÞB]

I am a little cynical... did the mass compile step generate any warnings or errors? I don't have your codebase to mass compile myself.

Just trying to help you understand what may be causing your crashes...do you have error reporting turned on? NIER Services ...

[10Degree]

There were some issues, and we addressed all of them.  Again, a step we always carefully go through during LV upgrades.  We have been fighting with this for a while.  I did a re-install of LV at one point and seemed to fix things, but I think it was only temporary.  I am suspicious of corrupt LV components?  I built an EXE and installer for this app yesterday, made some changes today, built the EXE and installer again and now it crashes when loading a particular front panel plug-in.  Funny thing is that I did not even touch the code for the now crashing vi.  LV is rotting.

[Mark_Yedinak]

Do you separate your compiled code from source? We have pretty much marked all of our code that way and don't experience issues with upgrades. We still mass compile everything when we upgrade. Also, are you using any packed project libraries? We found that they need to be rebuilt when any code changes occur. We have PPLs using other PPLs. We rebuild all PPLs any time we change any of our PPLs.

[JÞB]

Just throwing it out to eliminate it.   You cleared the obj cache? 

[10Degree]

Yes, didn’t help.  I am uninstalling all packages installed through the package manager to see if there is a corrupt package issue. 

[10Degree]

Is there a way to decouple the source from the compiled code? How ddi I set that up to test?

[RTSLVU]

I usually wait for the SP1 patch before moving everything to a new LabVIEW version.

Still running LabVIEW 2017 SP1