LabVIEW crashes while developing code

[JoeLV1992]

My co-worker and I have having an issue where LabVIEW just crashes for no reason about every 20 to 30 minutes.  Any suggestions on what may be going on would be helpful.

[paul.r]

Need more information to provide any help. Can you share crash reports? LabVIEW Version? What type of project is it? RT, FPGA, Windows? How large is the project? Are you using lots of classes and libraries? Is it crashing while running code or just while developing? Etc etc etc - the more information you can provide, the more likely you are to get help and a solution. 

[JoeLV1992]

I am using LabVIEW 2013 SP1 on a Win 7 PC.  It is a Windows project with one GUI with about 400 files totaling 10 MB of file space.  We have 6 lvlibs, no classes.  The crashes occur during development and not running the VIs.  I have about 20 days worth of crash reports from LabVIEW Data\LVInternalReports\LabVIEW.  Crashes can occur when working on a build spec or working on a VI.

[billko]

Same computer?

[JoeLV1992]

Two different computers exhibit the same behavior at our company that are under the same "IT control".

[JoeLV1992]

These logs are from my PC.  But we have two computers exhibiting the same behavior.

[aputman]

This sounds to me like an IT problem.  Make them fix it. 

Could be the security software or antivirus is preventing LabVIEW from doing something important. 

Maybe there is a phone-home that is randomly kicked off and can't complete.

[wiebe@CARYA]

These recommendations might do something (but I'd be skeptical). Running LabVIEW as administrator might help though, or at least give more info if LV doesn't crash then. Reinstalling helps if things got corrupted, but changes that that happened on two PCs seems slim. Unless of course there is a IT problem.

Those crash reports don't expose anything (except your email address). It seems to be missing the last (interesting) part, compared to other crash reports I've seen. There are some ini file keys that enable more verbose debug output, but it's up to NI to provide them.

Do you do anything special? ActiveX, .NET, DLLs, etc.?

Maybe installed the PI compiler?

[JoeLV1992]

I was also thinking that this may be an IT/permissions deal as well.  LabVIEW is installed through software  center, and permissions may be changed for the user as compared to the "silent install" they perform.  I will try launching LabVIEW as an Admin.

Haha, I guess there is no sense in remaining anonymous anymore.  My name is Joe Collura, I am a CLA, and can't figure out why I have a LabVIEW crashing issue. 

We do have a dll from a third party vendor for the card we use.  The two development PCs we have that are crashing don't have the card in them.  I will have to check with my co-worker to see if he has experienced the "crashing" on the PCs with the card in them.  No we don't have any raspberry Pi in our development.  I will also see if there is a 32-bit vs 64-bit compilation of the dll issue here as well.  My PC has Win7/64 bit.  Curious to see what my co-workers PC has as well.

[wiebe@CARYA]

---

@JoeLV1992 wrote:

 Haha, I guess there is no sense in remaining anonymous anymore.  My name is Joe Collura, I am a CLA, and can't figure out why I have a LabVIEW crashing issue. 

---

Well, it's in a text file in a zip in a zip, so I won't be too concerned with web crawlers using it to spam you. Eventually (at the file will lose it's relevance soon) I think you can delete it from your files stored in your profile. Not sure though, just a thought.