LabVIEW 2010 crashes often when deleting multiple diagram objects

[johnsold]

It crashed on my Mac, LV10.0.0.  I have attached the crash log as generated by Apple.

Lynn

[altenbach]

Thanks guys! So apparently it's not just me and there is something potentially smelly here.

Ravens, are you on windows 7? (Mine is W7 enterprise). The way the OS handles the lockup might be different. As we can see from Lynn's report, apple seems to be a bit more aware about what the rogue application is doing.... 😉

On rare occasions I actually do get the W7 dialog where the OS is "looking for a solution", but typically not.

[RavensFan]

Mine is Windows Vista Home Premium 64 bit.  LabVIEW is 32 bit.

I just tried on my work machine a couple times which is XP SP3, but did not see any problems.

[Neil.Pate]

Experienced very similar crashes on quite a simple BD. Just deleting a node with some broken wire attached to it, and BAM! Thrown to desktop with no error messages.

This is LV2010f2 64-bit on Win7 Ultimate 64-bit

[Ben_J1]

I have passed this on to R&D under #256644.

[GabbyG]

Hi

I already started a similar thread.

my solution so far  is to give Labview some time between selection and deletion.

I have the DEL button as shortcut on my mouse. So I could be very! quick.

Now that I take a breath between the two it seems to be more stable.

Gabi

[johnsold]

When I restarted LV later yesterday, LV offered to Investigate the Failure.  At the time I was busy with something else so I just cancelled.  This morning it occurred to me that the LV crash log might be of value to NI as well as the Apple log I posted yesterday.  So, I crashed LV again this morning with the BlurBenchmark VI and saved the crash log.  It Is attached.

Lynn

[wolson]

I am using LabView 2010 Developer on a Windows 7 64 bit dual processor computer. I am working with a large control program originally written under LabVIEW 8.6 and making some major modifications to it.

I am experiencing LabVIEW crashes fairly frequently after about 20 minutes of work. I am moving a number of icons around, renaming,  deleting and inserting new ones. My work just before the crash is not recoverable although work immediately prior to the operation that I was doing at the crash is. When I reboot LabVIEW, it does ask for recovery. After recovery, I can repeat the exact same operation that I was doing at the time of crash with no ill effects. Therefore, I do no think the crashes are directly connected to what I am doing at the time of the crash.

My guess is that LabVIEW 2010 is exceeding a defined buffer after so many minutes of operation on the 64 bit Windows 7 family.

[stbe]

I don't know whether you already have a "complete" bug description, but since it happens to me on both XPx86_SP3 and Win7x64 machines I give you my information:

Whenever the source of a wire has been deleted, LV crashes when further parts of a broken wire are removed.

It's reproducible with a quite simple test-structure... just delete the error in first, then any arbitrary part in between the remaining wire:

My work-around includes to delete the complete broken wire (not just parts) by tripple-clicking it ... then it works.

regards

[Timmar]

Yup, I am seeing it on 2009 on a 32bit XP machine.

I hadn't realised its "delete multiple objects" nature.

Thanks for the insight. Now I know what it is I can work around it.