LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

LabVIEW sure loves to crash for stupid reasons.

Unfortunately, my problem is with the IDE, not my built executable, I don't think PerfMon is going to be helpful since my crashes are so random and not repeatable (or the sequence leading up to any crash is not repeatable or even recordable...that would take months).

0 Kudos
Message 21 of 40
(2,140 Views)

Oh, and if you use version control make sure not to update or revert any files that LabVIEW has in memory, that tends to make things go bad really quickly.

0 Kudos
Message 22 of 40
(2,127 Views)

LV crashes are an annoying thing for sure.

However, my experience is that most crashes are generated by system configurations and/or 'dangerous' software alongside of LV.

OK, there are crashes of LV which are pure LV stuff (e.g. the mentioned DVR stuff), but NI is used to cover many of those crashes by the hotfixes ("f-patches").

My experience is that a corrupt LabVIEW.ini can greatly increase the number of crashes. I am not sure how that file could get corrupt from LV point of view, but i had that situation twice when using an ini from an older version of LV with a new version (e.g. copying the LV 2013 ini to LV 2014). Creating a new ini (delete 'corrupt' one while LV is closed and then start LV; it will create a new default ini) did the trick in these two situations.

Also for larger projects, external items like DLLs (both ANSI C and .NET) and network items (shared variables) could increase the risk of crashes.

 

I also recommend to use Windows Event Log and PerfMon to further dig into the issue, esp. if NI support is not able to reproduce things. Checking for firewall and anti-virus software is also often a good idea.

 

Norbert

Norbert
----------------------------------------------------------------------------------------------------
CEO: What exactly is stopping us from doing this?
Expert: Geometry
Marketing Manager: Just ignore it.
0 Kudos
Message 23 of 40
(2,114 Views)

That is the same issue I am having. LabVIEW only crashes when I am doing development, not running the apps. the crashes are also random and not repeatable. I am getting upwards of 12 crashes within a 3 hour period several days in a row. I also have had trouble tracking down exact cause.

0 Kudos
Message 24 of 40
(2,089 Views)

I'm in LV2014, unable to update to 2016 at this time but i get crashes on a regular basis.  It seems to mostly be due to classes.  It seems like the object cache has a bad habit of getting corrupted.  Usually clearing the object cache and opening the class control will solve the issue.  However, thats assuming hte project loads.  If not its a fun task of opening each class individually outside of the project window from windows explorer.  

0 Kudos
Message 25 of 40
(2,065 Views)

LabVIEW still crashes for me all the time.  What is going on?  Anyone still experiencing this?

0 Kudos
Message 26 of 40
(1,328 Views)

Very occasionally in normal LabVIEW development work (about once a week maybe and I work every day with it in different versions), much more frequently when DLLs are concerned.

 

And that is always the main suspect! If your application interfaces to DLLs and you get frequent crashes, that’s where you need to look. If those DLL interfaces were done by yourself and you are no C programming crack, knowing exactly how a C compiler works, chances are 99% that its caused there. If it was done by a third party like an instrument manufacturer, it’s usually the same.

Most developers creating such interfaces declare victory as soon as it doesn’t crash immediately on execution of the simple test cases they write. But for most DLL interfaces that is in fact where the real debugging effort starts. That it doesn’t crash right away only proofs that you took care of the most glaring buffer overrun, memory corruption, and threading issues. Now starts the real work of getting those nasty buggers out that still corrupt memory somewhere, sometimes, somehow!

Rolf Kalbermatter
My Blog
Message 27 of 40
(1,307 Views)

No DLL's in this case.  A large project though.

0 Kudos
Message 28 of 40
(1,294 Views)

What is large? My projects frequently contain several 100 to even 1000 VIs. But I do tend to modularize with lots of subVIs, so my 1000 VI project may be someone elses 300 VI project. And that is for sure another source of trouble. Another thing in my projects, I seldom use features that were not at least present in 3 or 4 versions prior to the currently used version. It has served me very well.

Rolf Kalbermatter
My Blog
Message 29 of 40
(1,286 Views)

@BigApple0 wrote:

LabVIEW still crashes for me all the time.  What is going on?  Anyone still experiencing this?


Adding to a six year old thread with absolutely no tangible information except a "me too" is not really useful. I am sure that whatever caused LabVIEW 2014 to crash has long been fixed.

 

I recommend to start a new thread and provide significantly more information:

 

  • What is your LabVIEW version
  • What is the definition of "all the time"? (every minute? once per day? random? whenever you specifically do something? At edit time or run time? etc.)
  • How does it "crash"? (locks up? crashes to desktop? computer bursts into flames?)
  • What does the program do?
  • Do you get a chance to send crash reports?
  • etc.
0 Kudos
Message 30 of 40
(1,273 Views)