The acquisition program runs continuously for 2 days, cannot use probe debugging, and reports an error

[阿银丶Ryan]

Hi all,

I am developing a data acquisition program using LabVIEW 2016 (64bit).

I am continuously acquiring data and logging it. When I finish logging, a modal window pops up to select the next action to be performed.

But when I click on stop logging, I find that the modal window does not pop up and the error report pops up on the graph.

During this time, the probe I added does not show the program running status.

I have continuously monitored the memory and no memory growth has occurred.

Any thoughts to help me find the exact problem.

The original program is a huge project so I can't give that.

[wiebe@CARYA]

---

@阿银丶Ryan wrote:

The original program is a huge project so I can't give that.

---

Fair enough. But giving nothing is on the other end of the information spectrum...

Can you reproduce this with a test that doesn't take 2 days?

What is the smallest possible way to reproduce this error?

That doesn't look like an error window. Does LV crash after it? Or is a One Button Popup your error handling?

You'd need to establish if this is a problem with the duration of the test or not. My guess would be it's a result of something you're doing wrong. If not, it's a seriously  weird bug. 

[阿银丶Ryan]

It is not necessary to run continuously for 2 days, but you can be sure that two hours of continuous operation is not a problem.

The program has a real-time interface refresh, data logging, and monitoring of data operations.

Therefore, I am struggling with how to build a minimally reproducible program.

The program does not crash when I click OK.

I wonder if all my programs are running in the UI thread and are overloaded.

Do you have any good ideas to locate the problem?

[zou]

You don't have to show us the whole project, just the VI calling the modal VI and the modal VI will be enough.

This kind of warning usually shows up when you manually open a modal VI while the calling VI is running.

Is this modal VI called in multiple place?

How do call this modal VI?  How do you close this VI?

An easy way to avoid this kind of problem is set the modal VI at runtime using property node instead of set in the VI properties dialog window.  And set it back to normal before close the VI.