Advice needed on finding LabVIEW crash

[jdunham]

I have a large application (2600 vis) in LabVIEW 8.2.1 which has recently started crashing at runtime, where crashing means that a dialog box comes up and says "LabVIEW 8.2.1 needs to close, do you want to tell Microsoft about it?".  Usually when this happens, LabVIEW is unresponsive, and I crash out and start over. 

In this case, the development environment is still usable, as long as I don't make the send/don't send decision on the crash dialog box.  My displays continue to update with new data received at the serial ports, and I am able to use execution highlighting to find exactly which VI(s) are stalled and where.  The problem is that the locations are seemingly random (it's always a different place) and most of the code has been running reliably for months or years.  Some of the stalled locations have included a flatten to string function, or else a FOR loop running on a small array with no other variables. 

It remains running indefinitely until I press the "don't send" button, and then everything shuts down immediately.
Sometimes the crash happens soon after startup, and sometimes it runs for 30 minutes or more without crashing, though it usually crashes within the hour.  Sometimes it writes a crash log (lvfailurelog.txt) but usually it doesn't.

This leads me to believe something else about LabVIEW is crashing, or some other piece of my code (there are many loops in parallel).  Obviously I will try to hunt for the problem by removing code until the problem goes away, but I was hoping for insight on what parts of LabVIEW could crash this way while still allowing LV to execute code and manage front panels.  I'm hoping to narrow down the search because I am not looking forward to the tedious task which awaits. 

One other piece of information is that I have LabVIEW 8.5 beta installed, but that has been installed all summer and the problem only started recently. I have built executables and given them to other testers, and they are crashing too.

Any advice?

Thanks,
Jason

[M_Atif]

For me its not the Labview, You need to increase the Memory- RAM of your PC, Mostly this error comes due to RAM problem.

But 2nd chance is that Your code may have some extra loops, so you are not releasing your memory after completing the loop.

It is the memory that is creating problem.

Atif

[Kodeeswaran]

please check how much memory does your application is consuming while processing, i hope that some support files might cause problems, use debugging options in application to locate the errors,

[altenbach]

---

@jdunham wrote:
I have a large application (2600 vis) in LabVIEW 8.2.1 which has recently started crashing at runtime,

---

Maybe you can narrow down the problem to something that happened "recently". Are you still working on this project? Does it also crash if you restore the code from before "recently" from backup?

Is the code all LabVIEW or do you call third party drivers or DLLs? Did you install any other software? Did the problem start after a windows update?

Does the code run fine until the crash: Correct behavior, correct results, all normal?

Start task manager before starting your application. Does memory use increase with time? Is CPU pegged at 100%?

[jdunham]

---

@altenbach wrote:

Maybe you can narrow down the problem to something that happened "recently". Are you still working on this project? Does it also crash if you restore the code from before "recently" from backup?

Is the code all LabVIEW or do you call third party drivers or DLLs? Did you install any other software? Did the problem start after a windows update?

Does the code run fine until the crash: Correct behavior, correct results, all normal?

Start task manager before starting your application. Does memory use increase with time? Is CPU pegged at 100%?

---

Hi Christian:

All great suggestions which I am pursuing.  We have been making changes to the code, but there is a lot of stuff going on and since this crash is not always happening in the same place, I am concerned that it is not directly related to a specific VI.

I am sort of hoping someone from NI could tell me which part of LabVIEW could crash such that some or all of the execution threads are still running and the development environment is still responding to keyboard and mouse input.

[jdunham]

OK, The crash turned out to be some changes to one of the DLLs we call.  Thanks for all the suggestions.