LV 8.6 crashing during block diagram edits?

[cebailey]

We installed LV 8.6 yesterday and have since had crashes during editing of the block diagram. The messages say something about DrwgMgr (sp?). LV reports an unrecoverable error, then exits, losing unsaved work. We're going back to the previous version now but worry about being able to stay current.

Any ideas?

Thanks!

[andre.buurman@carya]

Is it possible to post a VI that displays the problem?

[Hillman]

Hi,

Thanks for the post!

I would agree, seeing the code would help in this case. So please do supply it.

I will look into this further tomorrow - regarding DrwgMgr error (when Im in the office).

However, generally, 99% of the unexpected labVIEW behaviour I have seen is caused by a BAD installation, which seems by itself is just luck... Did you download this OR use the DVDs? - Or I guess, how did you install this?

I know it takes time, but I would recommend (unless it looks code related, in the sense that it doesnt happen when you edit any block diagram), to re-install. I would suggest following the following steps, (2nd post by myself) they are the standard guide for this process, and they regular sort out such problems.

Please give us an update,

Kind Regards,  

[cebailey]

OK, I have posted a VI that displays the problem. In my experience, editing this VI's block diagram for several hours will crash LabVIEW's environment. From its posted state, I had edited this particular VI for perhaps a further five minutes. In particular, if you look at the loop commented "THIS LOOP INTERPRETS MOTOR RESPONSES...", inside the True case, I was editing the innermost Case structure, putting copies of the Position, Moving, ComPend and Status local variables inside it and writing to them from constants, in each case as I added cases. So, I had been editing in LabVIEW for about 1.5 hours, saving every few minutes, and this was the last save before a crash. I've had crashes while editing different VIs.

But, I still don't see how this can be a code problem. The VI isn't what is crashing - it has all sorts of incomplete work in it - terminals unwired and so forth. I don't want any advice on how to make this VI run. This VI ois obviously not supposed to run yet. I just want to be able to edit the block diagram for more than a few hours without the LabVIEW development environment crashing.

You could easily write a VI that has a race condition, or that uses a Boolean control in a way inconsistent with its mechanical action setting, or that can never finish its while loop. How do you write a VI that crashes LV while you edit it?

[andre.buurman@carya]

I don't see how editting this code would crash LV. In my installation it doesn't crash.

Have you tried the suggestion of Hillman already. Looking at his answer it seems they have had multiple issues regarding faulty installations of LV 8.6.

[Hillman]

Hi Cebailey,

Thanks for the update.

I have to agree, how do you write a VI that crashes LV while you edit?

A) A bad installation of labVIEW.

I have heard of numeric control, whom value changed when the vi wasn't running! 

You need to follow the advice I gather you, using the msiBlast, to give you computer a FRESH start.

Let me know how you get on please,

Kind Regards,

James. 

[cebailey]

We have rolled the system back to 8.51. So far, there have been no problems. I think we have to outlaw software updates on the system, unless we start a new development project with it.