windows cannot find file

[Elsa Fung]

Hi!  I'm new to LabVIEW (been using it for 2 months).  For some reason, as time goes by (after I install it), LabVIEW crashes more and more often.  At the beginning, it crashes (just quit itself and ask if I want to send an error report) once in a while, but would be fine again when I restart LabVIEW or the computer.  Today, I edited a sub VI and included in my main VI, then when I ran it, LabVIEW crashes again (and gave me the option to send or not send the error report).  I restarted the computer and tried it again, and the same thing happened (NOTE: LabVIEW crashed at a different sub VI that was working properly before, so I don't think it was because I edited a sub VI earllier).  I tried it a several time and still the same thing happened.  Then I turned off my computer (thinking I might have had it one for too long), and waited about half an hour until I tried it again.  This time, when I double click on a VI to open, it took a long time to open LabVIEW and then an error popped up saying "Windows cannot find so-and-so.vi.  Make sure you typed the name correctly, and then try again.  To search for a file, click the Start button, and then click Search".  The worst thing is, after the error popped up, LabVIEW opened the file that was not found.

I'm thinking it might be related to project problems.  I had my main VI in a project before, then I deleted the project and the alias file.  Could that be it?

Thank you.

[WNM]

I've seen this behavior too (WinXP) when trying to open a VI (often part of a large project) and the system was otherwise busy with other tasks as well. I think Windows has its own timer and if a window doesn't finish opening by the time it times out then you get the error message. While this might be a clue that needs to be considered in solving your problem, I don't think that it is a particularly significant one; it's just what Windows does when it takes a while for a window to open.

I have not had a problem with my LabVIEW (v7.1.1) crashing.

You might want to do a thorough examination of your system to see if you have anything running in the background that would make the system slow to respond or unstable.

Good Luck!

[Elsa Fung]

Thanks!

I think I know what's wrong... (using too much memory)

I replaced calls to sub VI with the actual diagram, and it works total fine...

I think LabVIEW reserves spaces in memory when calling sub VIs and don't release them after the sub VI is finished...  I guess I just shouldn't use sub VIs now..

Thanks anyway!!

[PJS]

There is a primitive called 'Request Deallocation' that is suppose to free up resources in a VI after it is called.  You could try using this.

[Elsa Fung]

really?.. hmm.. where can I find the primitive?

Thank you ^_^

[Elsa Fung]

found it, but it still have the same problem (quitting by itself and ask me if i want to send an error report)

Thanks anyway ^_^

[Ankita]

Hi Elsa,

I would suggest selecting the "send report" option the next time LabVIEW crashes. When you select that option, an email with the error log will be sent to National Instruments support team who will in turn send the log to R&D team for investigation. It would be helpful if you could include the VI that is causing the crash and explain the workaround to avoid the crash. 

Regards,

Ankita

[Elsa Fung]

ok, thanks!

[Jimmy168]

Dear All,

I have encountered this problem, too. I did one experiment that I can open the vi well without calling the subvi and I open the vi well with calling other subvi. Only calling the subvi, the problem happened. I don't know why. Also, I can open the VI well with calling the subvi in some computer so i don't know it is related to the computer configture.  how did you solve this problem. Would you please advise? Thanks!

best regards,

Jimmy  

[Jimmy168]

hello, I have encourntered this problem. How did you solve it before? Would you please tell more information?thanks!