Mass compile crashes LabVIEW 2010

[AKA_TG]

Before I go ahead and call the support line

Pentium 4  

2.8GHZ

2GB RAM

XP 32 bit

Anyone have issues mass compiling an application code from 8.6.1 to 2010 SP1 whereby it would seem to work fine for quite awhile then crash?

I tries no cache on the VI and all other items are off.

It seems to happen even in subdirectories of the application.

I just installed 2010 SP1 and the device drivers and when I look at them in isolation they seem to be installed correctly.

I can also load the 8.6.1 application

Im just wondering if Mass Compile is running out of memory and is it known issue or am I discovering something.

I will attempt to log results on the next try.

[JtotheB]

Hey AKA_TG,

Were you able to consistently crash LabVIEW using the mass compile, or was this a one time issue?

[AKA_TG]

Sorry John,

I got through it by loading the project into labVIEW

I'll put this one in the  "Transferring up wards from 8.6.1 to 2010" category of LabVIEW headaches.

There are numerous other files in the project folder but I compiled only the ones that LabVIEW referenced in the project

by loading it and letting LV do its thing,. No crashes this way.

.

This at least allow me to continue my work and not be stuck.

As to if I could make it fail agin?  I Probably could!

But since there is no real time for hindsight (where I work ) I'll have to leave it up to others to figure out if there is a problem with it.

Thanks!

[richjoh]

I went from LV2010 to LV2010SP1. Yes, LV2010SP1 compiler is new (so recompiling required) and I noticed the compiler could not find my broken link Type Def that was just fine in LV2010 compile.

Then after fixing that, my only issue is the LV2010SP1 compiler tells me I'm missing a lvclass but I deleted this class many version ago when trying to decide whether to go with a class or not. There is not a class in the project the class identified below were deleted and removed from the project. Huh explain this....

""

[richjoh]

There is a menu under Tools Advanced "Clear Compile Object Cache". Never use this before so I'm not sure its my problem cure. It shows two item, i386 and Labview to clear. i386 is larger than labview. Maybe I need to clear Labview and redo mass compile... anyone do this yet? The context help doesn't say much.

My guess is the lvclass object code still persist although I deleted the class from the project....

[richjoh]

Clear compiled object cache does nothing in regard to why a deleted lvclass appears in the compiled results.

I restored the 3 files (2 lvclasses and a ctl) and the mass compile reported NO errors (and my jaw dropped). These 3 files were no longer a part of the project when I used old LV2010.

LV2010SP1 new compiler links & build them INTO THE PROJECT FOLDER (although they are in the recycle bin) as you can see the compile error in the picture above. On the other hand, the old LV2010 worked just fine on compiling. My SP1 executable will not run without adding these unnecessary unused lvclass files.

Any work around or patch for this issue?

[AKA_TG]

Clear compiled object cache does nothing in regard to why a deleted lvclass appears in the compiled results.

I restored the 3 files (2 lvclasses and a ctl) and the mass compile reported NO errors (and my jaw dropped). These 3 files were no longer a part of the project when I used old LV2010.

LV2010SP1 new compiler links & build them INTO THE PROJECT FOLDER (although they are in the recycle bin) as you can see the compile error in the picture above. On the other hand, the old LV2010 worked just fine on compiling. My SP1 executable will not run without adding these unnecessary unused lvclass files.

Any work around or patch for this issue?

I know I am not much help but I gotta ask how you compiled. Is the lvclass file still on the disk in a subdirectory where the mass compikle is taking place?

My work aropund was to load the project file and all the VIs into memory that the project will use then they compiled correctly when the

VIs are brought into memory by LabVIEW. Then I do a save all.

(I got me one big VI containing all source VIs my project will use.)  I know it sounds wacky but it actually works for me and there are probably others that do the same thing just to be sure all VIs are referenced properly.

Regards,

[Paul-D]

Hey guys, this is Paul with Applications Engineering at NI.

I have reviewed your issues, asked around, and have a couple tips and questions.

First, if there is any chance you could post your project in a zipped format, then we could examine it on our end and see if we experience the same issue, which would make it easy to file a CAR on.  If you are wary of posting your code publicly, you can PM me, and we can work out a way to upload it to our FTP server that only NI employees can access.

richjoh, in your posted Mass Compile screen, I see a VI being flagged as bad.  When you open this VI on it's own do you experience this problem?  Can you locate in that VI where it calls the NanoMsg.lvclass?

Second, to either of you, were the controls and lvclasses mentioned still referenced in your projects anywhere?  Were they included in the dependencies?  If not, once you restored these files into the project, find them in the

dependencies, right click them, choose "Find">"Callers".  Where they still being called anywhere?

Alternative to your solutions, have you considered creating a new project and adding all of your VIs into the new project?  I have seen this resolve upconverting issues in the past.

[richjoh]

FYI, after taking a thorough second look at my code, I deleted the lvclass like I mentioned but I forgot about the class's methods (a getxxx and setxxx whatever) that remained in the auto-populating folder. Since the folder was including all my VI files the compile went searching for the lvclass. Problem solved,  my bad.