10-01-2010 01:12 PM
I found an odd LabVIEW 2010 bug that will cause a hard crash. The bug appears to be related to how LabVIEW operates on data in-place and some interaction between clusters, arrays, and the Aum Array Elements node. It's hard to describe verbally, so I'll just draw you a picture
LabVIEW 2010 CRASH.vi (16.56K)
10-01-2010 03:08 PM
No crash on my system: LV2010, W7 64-bit, Pentium E5200
10-01-2010 03:18 PM
Does not crash on my Mac.
Lynn
10-01-2010 03:29 PM - edited 10-01-2010 03:30 PM
It crashes mine. No error messages, no nothing. Just bam, LabView is not running anymore.
LV 2010, Windows XP
10-01-2010 03:35 PM
Jack: Are you running LabVIEW 64-bit or LabVIEW 32-bit on your W7 64-bit OS?
10-01-2010 03:39 PM
I'll add that I've seen this crash on LabVIEW 2010 32-bit (including with the 2010 f2 patch applied) on both Windows 7 64-bit and Windows XP (32-bit). Note: I haven't tried LabVIEW 2010 64-bit.
10-01-2010 04:00 PM
I'm running LV2010 64-bit.
10-04-2010 09:28 PM
Hi Jim,
This was reported to R&D (# 252210) for further investigation. It looks like you've pretty much covered this and the possible workarounds. Thank you for being so thorough!
10-08-2010 11:48 AM
Could someone link where this has been covered well, with workarounds? I dont see a fix.
10-08-2010 11:56 AM
@rex1030 wrote:
Could someone link where this has been covered well, with workarounds? I dont see a fix.
Jim linked a thread on LAVA. It appears he worked with NI support dirrectly since he reported a CAR number.
I know of no work-arounds aside from avoiding the data construct.
Ben