Sorry for the inconvenience.

[Neil.Pate]

Help!

I have an app which has been running ok for a while now, and this morning it failed with LabVIEW crashing and burning.

The error message was the dialogue where it says "LabVIEW 8.6 Development System has encountered a problem and needs to close..."

I have seen this error message before (in the stangest places), but exclusively in development mode. This error occurred during Run mode, and after several hours of doing the same thing (i.e. if something was borked in the s/w it should have failed much earlier). Can a dodgy driver / DLL call give this type of error message? As it so happens I don't particularly trust the industrial single-board PC and PCI backplane as there is lots of odd behaviour there.

Any ideas?

[Greg_S.]

Hi,

It happens for me one time, it was a memory problem, after few hours memory for LabVIEW was increasing too much.

Your problem is repeating always after a few hours ? Memory allocated to labVIEW is not increasing ?

Regards

[Mathan]

---

nrp wrote:

Can a dodgy driver / DLL call give this type of error message?

---

Off course a wrong pointer to a call to a function to a dll in the application will results in such kind of error messages. Double check the call to the dll.

Have a look at this thread also

Mathan

[tst]

You should note that the message itself has nothing to do with LabVIEW. It's a standard message that Windows displays for any process which crashes. This means that you can't really infer anything about the reason for the crash just from seeing it.

That said, the window should have an option for displaying more details and for sending the data to Microsoft. This can help you narrow down the options for why the crash happened. I suggest you also send the data to MS, because if they ran into this before, they will point you to a web page with the details.

[Mathan]

---

tst wrote:

You should note that the message itself has nothing to do with LabVIEW. It's a standard message that Windows displays for any process which crashes. This means that you can't really infer anything about the reason for the crash just from seeing it.

---

It may not be like that. Here is another magic control thread that discusses more reasons and a workaround.

Mathan

[tst]

I didn't say the crash was not caused by LabVIEW. I said the message itself does not come from LabVIEW, so you can't learn anything from the fact that it appeared about the cause of the crash. You can use the details in the message to try and find the cause, however.

[Ben]

The system event log may have some bread crumbs to follow...

Ben

[Mark_Yedinak]

More likely than not you are encountering a memory leak. While your application is running check the memory useage under Windows task manager. If the memory is ever increasing you do have a leak of some sort. It could be the dll itself.

[Neil.Pate · Accepted solution]

Thanks for all the suggestions everyone!

Just got back from the client and debugging the problem. It was a really weird error message which actually came up on the screen while another VI was running (and continued to run fine, with me able to probe the block diagram etc!).

The culprit was.....a  TDMS write! In another loop I was closing the file reference, and then trying to write to the TDMS file using the now closed reference.

In retrospect I have seen these kinds of errors a lot with TDMS, when there is an error its not exactly a graceful shutdown!