LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

labview suddensly shuts down automatically

Hi,

I'm having trouble with an application I wrote in Labview. I wrote a vi, which is called in a main vi (my main program). When I run the vi seperatly, I have no problem. When I call the vi in another program (also written in labview), after a few minutes, labview shuts down without any error message (not even a windows error).

Does anybody knows what causes this?

thanks,

best regards,
marino
0 Kudos
Message 1 of 8
(3,422 Views)
Hi,

Do you use anything 'exotic'? E.g. DLL's ActiveX, CIN's.

Do you use references of any kind (to controls, vi's or application)?

It's probably caused by one of these things, or a memory leak-ish thing.
You'll have to tell use more about the vi.

Regards,

Wiebe.

"marino" wrote in message
news:5065000000080000001F730000-1042324653000@exchange.ni.com...
> Hi,
>
> I'm having trouble with an application I wrote in Labview. I wrote a
> vi, which is called in a main vi (my main program). When I run the vi
> seperatly, I have no problem. When I call the vi in another program
> (also written in labview), after a few minutes, labview shuts down
> without any error message (not even a windows error).
>
> Does anybody knows what causes this?
>
> thanks,

>
> best regards,
> marino
0 Kudos
Message 2 of 8
(3,422 Views)
yes...

Before I call the vi, I use a dll (written in delphi) to access databases. But I don't think the dll causes this because we've been using it for years.
The vi is a part of a sequence of vi's. First I call a couple of vi's which use the dll, and then I call the vi (which closes labview automatically after a few minutes or seconds) This vi doens't use any dll's.

best regards,
Marino
0 Kudos
Message 3 of 8
(3,422 Views)
Hi,

You could try to put the suspect vi in the true state of a case, and wire
false to it (in the original sequence). You could put a few minutes wait in
the true case. If it still crashes, it's not the vi, but a late reaction of
the dll. Just to make sure...

The VI does't crash when you run it alone. Does it crash when it's called
from the sequence, but without the inputs wired? Perhaps the crash relates
to an input value.

If it is the VI, we still need more info; e.g. are there large arrays, shift
registers (esp. unwire from outside), etc.

Regards,

Wiebe.


"marino" wrote in message
news:506500000005000000AECA0000-1042324653000@exchange.ni.com...
> yes...
>
> Before I call the vi, I use a dll (written in delphi) to access
>
databases. But I don't think the dll causes this because we've been
> using it for years.
> The vi is a part of a sequence of vi's. First I call a couple of vi's
> which use the dll, and then I call the vi (which closes labview
> automatically after a few minutes or seconds) This vi doens't use any
> dll's.
>
> best regards,
> Marino
0 Kudos
Message 4 of 8
(3,422 Views)
Hi,

The VI doesn't crash when I run it alone and it has almost no input parameters (a string which is fixed and the error clusters)

The vi is a little sequence of its own. It consists of a for loop and in this for loop there is a while loop which polls to the OK or STOP button. Each time one of these buttons is pressed, the while loop stops and the index of the for loop (the main loop) is increased and the while loop is executed again until the number (which is wired to N of the for loop) is reached.

When I run the vi alone, everything is ok. When I run this vi in a sequence whith other vi (which use a dll), it stops after a random time (shuts down labview completely)

best regards,
Marino
0 Kudos
Message 5 of 8
(3,422 Views)
Hi again...

another thing that I must mention is that I saved the vi into an llb (together with the vi's that use the dll). I've saved it for "application distribution" (without the diagrams). When I call the vi, it works ok (so far)... when I call it from the llb, it crashes...

Maybe this can help you find what is going wrong...

best regards
Marino
0 Kudos
Message 6 of 8
(3,422 Views)
Marino,

Perhaps it helps if you mass compile the llb (Tools>Advanced>Mass compile).
It shouldn't crash, but the only thing I can think of that's different
between the VI and the VI in the llb is if it is (or any calling VI's are)
compiled or not.

Regards,

Wiebe.

"marino" wrote in message
news:5065000000050000008CCB0000-1042324653000@exchange.ni.com...
> Hi again...
>
> another thing that I must mention is that I saved the vi into an llb
> (together with the vi's that use the dll). I've saved it for
> "application distribution" (without the diagrams). When I call the vi,
> it works ok (so far)... when I call it from the llb, it crashes...
>
> Maybe this can help you find what is going wrong...
>
> best regards

> Marino
0 Kudos
Message 7 of 8
(3,422 Views)
hi again...

Thank you for the mass compile tip... it worked. But I now have the same problem when I use the comm port while running the same vi (in the sequence).
The vi ran stable until I opened the hyperterminal on com1 in windows (while the vi was running in the sequence). When the hyperterminal was running, labview shut down after a few seconds...

what can I do about that?

thanks

best regards
0 Kudos
Message 8 of 8
(3,422 Views)