I copied & paste a paragraph of an email I received earlier regarding "insane object" for your reference.
What does an "insane object" error mean and what should I do?
This message means that an object in LabVIEW such as a wire or a loop
tunnel does not pass an internal test known as a sanity check. If the
errors are serious enough, LabVIEW exits because something has become very
corrupted. Sanity checks occur before each save, to ensure that corrupted
VIs are not written over good VIs. They also happen as part of the compile
process. Thus, sanity checks happen frequently. Many insanities are
actually fixed (made sane) after the dialog box appears and will not appear
again, so the first thing you should do after receiving an insane object
error is to try to make a backup copy of the VI, run it, and perform some
additional editing to see if the problem was resolved automatically.
VI corruptions do not happen often. They can happen because of disk
corruption, but this will often lead to a file that can no longer be
loaded. Corruptions can also happen because the programmer did something
that corrupts a LabVIEW data type, perhaps as the result of a call to
external code. The following are examples of insane object errors:
Insane Object at BDHP+4D50 in 'sksks.vi': (graphics) (0x80):wire segment
(WIRE)
Insane Object at BDHP+5CA0 in "CAPL3.vi": (graphics) (0x80):loop tunnel
(DCO)
In the first example above, the error message itself gives information
about which object is insane. BDHP means the offending object exists on the
block diagram heap, as opposed to the FPHP for front panel heap. The +4D50
is the hex offset in the heap where the object is located. The "Wire
Segment" text indicates that the object is a wire object. The "graphics"
text indicates that the insanity is graphics-related, which means it is not
serious and will most likely be repaired automatically.
The second message above is similar, but refers to a loop tunnel (i.e., the
tunnel formed where a wire crosses the edge of a loop) rather than a wire.
If you receive an insane object message, it is best to delete and recreate
the most recently created objects on either the front panel or block
diagram, depending on whether the error message contains "FPHP" or "BDHP".
Make use of the text in the error message in deciding which objects to
rebuild. In the case of the second message above, it would be best to
delete and recreate the most recently created loop tunnels.
Another workaround that works best if the VI is small is to select the
entire diagram and copy it to a new VI. After saving the new VI, there is a
good chance the insane object error will no longer appear. If the VI is too
large to cut and paste to a new VI and another computer with an identical
version of LabVIEW is available, you can copy the VI to disk (or to your
network if that is available) and open it on the second machine. If the
insane object errors do not appear, save the VI (on the second machine) and
transfer it back to the original PC (by disk or by network). The new,
uncorrupted version of the VI should now run without generating the insane
object error.
