LV crashes while loading my llb, but the built app. functions correctly???

[Jolty]

I�m hoping someone may understand the cause of the LabVIEW crash I�m experiencing.

LabVIEW 6.1 crashes and Windows 2000 says, "LabVIEW.exe has generated errors and will be closed by Windows" when I try to load an llb by clicking on the top-level vi from within LabVIEW or when opening the llb from outside LabVIEW. It crashes while loading particular sub-vi�s of the llb. If I try to load the offending subvi�s directly, I also get the same crash. If I build the llb into an application, the build goes smoothly and the resulting application functions correctly. If I use a �splash screen� approach and do not load the offending sub-vi�s (by not opening vi references to them), they load-up fi
ne when the top-level vi loads and then I am able to edit and re-save any vi of the llb including the offending sub-vi�s. I�ve tried re-saving the llb as a separate development distribution and still get the same crash behavior. I�ve also tried saving the offending sub-vi�s to separate files outside the mother llb (after getting them open with the splash screen approach) and I get the same crash when I open these files. If I save one of the offending sub-vi�s as a separate llb, I can�t get it open even with the splash screen approach. I�ve loaded the latest video driver for my Dell Inspiron 8100 laptop and I get the same behavior on a Dell Dimension 8200 desktop that is also running Windows 2000 (Version 5 SP4). There are 110 objects in my llb that includes *.vi�s, *.rtm�s, and *.ctl�s.. Any ideas as to why/how this is occurring and how I can fix it? Is this a known 6.1 bug that is fixed in 7? Any info would be greatly appreciated. I�ve included my splash screen like loader, f
or what it�s worth. Thanks.

[Ken_S]

Hello,

As I understand it you�ve basically got several subVIs which cause Labview to crash (on two different PCs) when they load, regardless of whether these subVIs are in an llb, etc. The only exception to this is when you build an application using these VIs or you use your splash screen program to load them into memory.

One thing to try to fix this would be to do a Mass Compile on the llb which contains these VIs. To do this, open a blank VI in Labview (you don�t have to open the llb to do this), and from the menu choose �Tools->Advanced->Mass Compile��. It will then prompt you for the location of the llb file. After choosing the llb file hit the �Mass Compile� button.

If this doesn�t fix the subVIs, could you post one of the offending subVIs so that I
could see if I can repeat the issue you�re seeing?

Thanks,
Ken S.
National Instruments

[Jolty]

Thanks for responding. Your understanding is correct. Mass compiling was one of the first things I tried (although I failed to mention it). I also un-installed and re-installed LabVIEW. It crashes during mass compiling of the full llb, although the vi that it appears to be working on when it crashes is not an �offender�, i.e. I can open that vi fine. The crash during mass compiling is the same crash, i.e. Windows says it had to close LabVIEW because it generated errors.

I�ve attached one of the offenders. It is missing many of it�s sub-vi�s so you�ll have to hit �ignore vi� a bunch when opening it. (The llb of it is ~2.6 MB. I thought that might be too big/rude to post.) This vi crashes LabVIEW upon mass compile or upon opening it (after hit
ting �ignore subvi� a bunch).

I was going to attach an llb of another smaller offender, but in the process of editing it to be a little prettier and better documented, the problem kind of vanished for that vi. The main routine still crashes when I mass compile the full llb, but now I can open some of the old offenders without incident. I still can�t open the main routine directly as it crashes LabVIEW. Thanks for your time.

[Ken_S]

Hello,

I opened your subVI in LabVIEW 6.1 and it crashed for me also. I was able to open the VI in LabVIEW 7.0 successfully, then I tried to save it for 6.1 from 7.0 and when I opened it in 6.1 again it still crashed.

So I think the subVIs or llb are definitely corrupted in some way. If you post your full llb file, I can try to find a way to uncorrupt it for you.

As an alternative, you could try and target all of the offending subVIs and �play� with them a little like you did with the ones that are now working. This might have the same effect on all of the offending subVIs. It may just come down to changing the subVIs just slightly so the subVI is saved in a different way.

Ken S.
National Instruments

[Lupita]

Hi,

I am having the same problem. I just got a LV 6.1 LLB that was running on a Windows 200 PC that I really need to open and I get the error: Labview.exe has generated an error and will be closed by windows. I tried mass compiling it but I got the same error. I believe the file is definitely corrupted. I also tried loading it

Could I send you the LLB to see it is possible touncorrupt it? If so, what is the best way to do so?

Thank you.

[Yi Y]

Hi Lupita,
There's a good chance that the library is not going to be revived if it's corrupted.  However, you can post it here, and I'll try openning it on different versions of LabVIEW and see what I get.

Yi Y.
Applications Engineer
National Instruments
http://www.ni.com/support