I've just finisched writing an application running perfectly under LV 5.1. Then I've updated to LV 6.02.
Now, when executing the a.m. app (written under 5.1) my whole system crashes (only ON/OFF of the PC is possible and it seems that it also affects the proper function of Windows), when calling individual (not all) sub_vi's.
"Philipp" schrieb im Newsbeitrag news:3b8371b5@newsgroups.... > > Hi, > > I've just finisched writing an application running perfectly under LV 5.1. > Then I've updated to LV 6.02. > > Now, when executing the a.m. app (written under 5.1) my whole system > crashes (only ON/OFF of the PC is possible and it seems that it > also affects the proper function of Windows), when calling > individual (not all) sub_vi's. > > NB: Mass compile has been executed already. > > Any idea what I can do? > > TIA Philipp > > > >
Hi, on running the app the the crash will occur, when employing an array of clusters.
If I want to edit this array in a diagram (i.e. not when running) the PC will crash as well.
"Philipp" wrote in message news:3b837ca7@newsgroups.... > > "Philipp" schrieb im Newsbeitrag news:3b8371b5@newsgroups.... > > > > Hi, > > > > I've just finisched writing an application running perfectly under LV 5.1. > > Then I've updated to LV 6.02. > > > > Now, when executing the a.m. app (written under 5.1) my whole system > > crashes (only ON/OFF of the PC is possible and it seems that it > > also affects the proper function of Windows), when calling > > individual (not all) sub_vi's. > > > > NB: Mass compile has been executed already. > > > > Any idea what I can do? > > > > TIA Philipp > > > > > > > > > > > Hi, > on running the app the the crash will occur, when employing an array of > clusters. > > If I want to edit this array in a diagram (i.e. not when running) the PC > will > crash as well.
I had a problem with LV crashing that was related to an array of complicated clusters. I was copying the array up to a custom control when LV crashed and then I couldn't open the VI without LV crashing again. I ended up deleting the custom control and that fixed it. Apparently it was corrupted. After that I went without that control, because I guess it got too complicated.
No guarantees, but I don't know what else could cause that. I am sure that the LabVIEW developers do, now that you indicated the source of the problem.