DWarn 0x7E4A7AB1: Nonfatal insanity (0x00000080) detected

[_Bryan]

I have been searching the fourms for some answers, but have come up blank so far.  I have read that you don't really have to worry about the nonfatal insanity warnings unless they come up all the time.  If I open this vi in LabVIEW and just save it, then close LabVIEW I get a error messages.

I noticed LabVIEW starting to act strange/sluggish while I am adding front panel decorations.  I am using thick lines to create a plumbing diagram of the system with booleans signaling if a valve is open or closed.  As I am adjusting the positions of the lines LabVIEW will just keep getting slower and slower and even hang for 10 seconds or so.  If I save and close the VI and then open it again it acts normal for a little while and then starts slowing down again.

And then if I close LabVIEW I will get the errors.  So is there any way to track down Nonfatal insanity errors?

Here is a single entry (of many).....

DWarn 0x7E4A7AB1: Nonfatal insanity (0x00000080) detected in'3 Leg 9 station Cascade_0031.vi:Instance:0: My Computer'
e:\builds\penguin\labview\branches\2011\dev\source\panel\fpsane.cpp(1016) : DWarn: Nonfatal insanity (0x00000080) detected in'3 Leg 9 station Cascade_0031.vi:Instance:0: My Computer'
minidump id: 0db0965f-980b-4d89-ab2a-db8326cf9297
$Id: //labview/branches/2011/dev/source/panel/fpsane.cpp#17 $
0x006A9243 - LabVIEW <unknown> + 0
0x10015F30 - mgcore_SH_11_0 <unknown> + 0
0x00C9D38F - LabVIEW <unknown> + 0
0x00D0D3EB - LabVIEW <unknown> + 0
0x00CC0A07 - LabVIEW <unknown> + 0
0x00F5D06B - LabVIEW <unknown> + 0
0x00DC4492 - LabVIEW <unknown> + 0
0x00CF2EA0 - LabVIEW <unknown> + 0
0x00E29EAA - LabVIEW <unknown> + 0
0x00D602AA - LabVIEW <unknown> + 0
0x00F5CC20 - LabVIEW <unknown> + 0
0x0103DDB2 - LabVIEW <unknown> + 0
0x0104660C - LabVIEW <unknown> + 0
0x01047D53 - LabVIEW <unknown> + 0
0x01048615 - LabVIEW <unknown> + 0
0x01048AEC - LabVIEW <unknown> + 0
0x0046DC40 - LabVIEW <unknown> + 0
0x01047D21 - LabVIEW <unknown> + 0
0x01048615 - LabVIEW <unknown> + 0
0x010489B8 - LabVIEW <unknown> + 0
0x016B2DED - LabVIEW <unknown> + 0
0x016B2EFB - LabVIEW <unknown> + 0
0x0164F7E7 - LabVIEW <unknown> + 0
0x00A3505D - LabVIEW <unknown> + 0
0x00A3526D - LabVIEW <unknown> + 0
0x00A35628 - LabVIEW <unknown> + 0
0x01B19404 - LabVIEW <unknown> + 0
0x01BB79E5 - LabVIEW <unknown> + 0
0x01B0D7AC - LabVIEW <unknown> + 0
0x01B37CE8 - LabVIEW <unknown> + 0
0x01BB6FD9 - LabVIEW <unknown> + 0
0x01B36F39 - LabVIEW <unknown> + 0
0x0044A560 - LabVIEW <unknown> + 0
0x0044A7FD - LabVIEW <unknown> + 0
0x0044A870 - LabVIEW <unknown> + 0
0x01CB8545 - LabVIEW <unknown> + 0
*** Dumping Bread Crumb Stack ***
*** LabVIEW Base Address: 0x00400000 ***
#** sanity checking heap: "C:\LabVIEW\Programs\9 Station Cascade\3 Leg 9 station Cascade_0031.vi\0"
#** Saving: "C:\LabVIEW\Programs\9 Station Cascade\3 Leg 9 station Cascade_0031.vi\0"
#** Saving: "C:\LabVIEW\Programs\9 Station Cascade\3 Leg 9 station Cascade_0031.vi"
*** End Dump ***

[0utlaw]

Hello _Bryan,

I've never encountered the nonfatal insanity warning you're seeing, but the development slowdown behavior sounds suspiciously like an issue I ran into with the LabVIEW undo cache that caused a slowdown when making large numbers of changes to VIs with large front panels. Out of curiosity- if you lower the "Maximum undo steps per VI" value in Tools>>Options>>Environment, does it reduce or eliminate the slowdown?

Regards,

[_Bryan]

I have not tried that yet, but I will.

I also wanted to add that I have mass compiled the VI and all the VI's I have created for the program.