LabVIEW 2010 crashes often when deleting multiple diagram objects

[Andromeda]

I also have seen this behaviour more times than I can count. LabVIEW 2010 seems to crash much more often than any previous version (and I go back to LabVIEW 2.0 beta).

I have a saved vi suite which reproduces this behaviour on my Windows 7 x64 machine, and also on an XP x32 machine. It happens with the unpatched 2010 release, and also with patch 4 applied.

Oddly, the tech support person assigned to this case says that he cannot reproduce the crash, so I would be curious as to whether others experience the same thing.

I mostly see this behaviour when doing major surgery to a VI - if there are broken wires in hidden case panels, it seems to trigger the crashes, but I don't have a systematic way to reproduce it from scratch.

[Ben_J1]

Andromeda,

   Is there a way you could post the VI which reproduces this behavior on this forum so others can test it?

Regards,

[Andromeda]

Here's the VI - I'm curious as to whether it also crashes other people's LabVIEW 2010 installs.

I was using 32-bit LabVIEW 2010 under Windows 7 x64.

Out of interest, I tried with a fresh LabVIEW 2010 install under 32-bit Windows XP, and reproduced the crash in that environment as well.

The VI only crashes under LabVIEW 2010: LabVIEW 2009 SP1 has no problem with it, if it is saved in LV 2009 format.

Drop the llb onto your desktop, open it, and select 3D circular buffer.vi.

Open the diagram (ctrl-E), and you will see a while loop containing two case selectors.

Attempt to view the False panel of the left-hand side case selector, by either clicking on the little arrows at the top, or by selecting False from the case pop-up selector.

LabVIEW does not immediate crash - in my two environments, it freezes for a period of several seconds before exiting.

I think that this may be the same problem with broken wires which was posted earlier in this thread - the wire source was deleted in an edit, but the broken wire was not removed (I don't usually remove all broken wires with ctrl-B, as it's easy to accidentally miss a wire which needs attention if I do).

[GabbyG]

Hi

I am sorry to not confirm this or the meandring Error line some postings before. (LV2010f4 on XP professional)

But since I am still getting frequent crashes of LV2010 I'll still be foolowing the thread.

Gabi

[Ricky_V.]

Hi Andromeda,

I tried your VI on my computer (Windows 7 32-bit) with LabVIEW 32-bit. I did not get any freezes or crashing. I did ctrl-B to remove the broken wires to see if that would make a difference, and it did not.

We will be following up with the Corrective Action Request (CAR) to see of any fixes.

Ricky

[Jon_S.]

Hello Everyone,

I wanted to further comment on the issue that has been reported (CAR 256644).  First off we closed this CAR as a duplicate and you should track this bug as CAR 254317.  The crash seems to occur when you are deleting sections of code that contain broken wires.  This doesn't happen every time there is a broken wire but only if a number of circumstances are present.

The best way to work around this particular issue is to use Ctrl+B to clean up broken wires first.

I want to thank everyone that supplied code that has helped us be able to reproduce and identify this issue.

[Andromeda]

Thanks for trying to reproduce this bug.

I'm curious as so what is different about my two LabVIEW 2010 installs, but if you can't reproduce the crash, there isn't a lot you can do.

I tried to reproduce the test reported earlier in this thread, in which a wire source was deleted, followed by a segment of the now-broken wire. I couldn't reproduce it on my machine (Win 7 x64, LabVIEW 2010 f4 x32).

[Andromeda]

I was wrong - the simple technique illustrated earlier in this thread does crash my machine - it just took a while.

In my case, the test vi was saved for recovery after the crash - when I selected it for recovery, LabVIEW froze completely. I don't know if that is useful information or not - there seems to be a pretty well defined CAR for the behaviour.

[Jon_S. · Accepted solution]

Hello Users,

I wanted to thank everyone that contributed time and code to help us define this issue.  I am happy to report that we have fixed CAR 254317 (originally posted CAR 256644 was closed as a duplicate) in LabVIEW 2010 SP1.  I'm not quite sure why it didn't show up in the bug fix list as it was tagged for inclusion.

Thanks again!