LabVIEW crashes with "Insane Object" error.

[pawel]

Hello

While editing a diagram I got (quite often) an error that "insane object" has been found. After that LabVIEW crashes.
I enclose error dialog boxes.

Can anybody tell me what is wrong?

I have LV7, W2k, Dell Dimension 1.5GHz, 500MB RAM and Matrox Dual Head graphic adapter.

Thanks in advance
Pawel

[shoneill]

Hi Pawel,

try copying all of the bolck diagram and pasting into a new VI and resaving. This works for me most of the time.

Hope this helps

Shane.

[Ray.R]

Hi Pawel,

I sympatise with you...

When I first uinstalled LV7, it was on a Dell Dimension 2350, running Win XP. The experience was horrible... I got that "insane object" message repeatedly.. I reported some issues in past postings:

http://exchange.ni.com/servlet/ProcessRequest?RHIVEID=101&RPAGEID=206&HOID=50650000001100000069060000&HCHOSEN=506500000012000000F6180000&HTHREAD=000006390&UCATEGORY_0=_49_%24_6_&UCATEGORY_S=0

http://exchange.ni.com/servlet/ProcessRequest?RHIVEID=101&RPAGEID=206&HOID=50650000001100000069060000&HCHOSEN=50650000001200000096190000&HTHREAD=000006370000006550&UCATEGORY_0=_49_%24_6_&UCATEGORY_S=0

http://exchange.ni.com/servlet/ProcessRequest?RHIVEID=101&RPAGEID=206&HOID=50650000001100000069060000&HCHOSEN=5065000000120000002A1
C0000&HTHREAD=000006473000007210&UCATEGORY_0=_49_%24_6_&UCATEGORY_S=0

In one of the LV7 surveys, I mentionned quite a few issues... (I can't find that post).

My solution was to move to a clone PC. Although the vi's have not changed, but the problem(s) dissappeared. As for the "insane object" message, I have never seen it since.

The graphics adapter on the Dell is an Intel 82845G.

If my memory serves me right, I would get that message by simply moving the mouse cursor over the LV block diagram. - very frustrating - :o(

Wish I could help you more...

JLV

[Ray.R]

Here is what some other posts say about thie error (from LV6):

http://exchange.ni.com/servlet/ProcessRequest?RHIVEID=101&RPAGEID=135&HOID=5065000000080000009B650000&UCATEGORY_0=_49_%24_6_&UCATEGORY_S=0

[pawel]

Hi Shane

That is an option, but the last one. I have a lot of setting for this vi, since it is the top level vi so it will take some time to resave it. But if necesary I will do it. Thanks.
Pawel

[pawel]

Hi Joe
Thank you for your help.
The situation which you describe is identically 100% with mine. I am trying to save vi and ... LV crashes.

In the mentioned post your teller says something about high resolution of the screen. That rings a bel, since I got dual head graphic adapter and two screens, which means that my resolution is 2048x768 !!! Maybe that gives LabVIEW hard times and causes so many troubles.

On the other hand, I do not want to give up my double screen. It is realy convinient to have front pannel on one screen and diagram on another.

Thanks for help

Pawel

[Ray.R]

Hi Pawel,

As a matter of fact, I am running two screens on the clone PC using a Matrox Millennium G550 video adapter. It works fine. 🐵

The Dell PC has a single display set to 1024 X 768. I use the Dell PC for emails and MS-Word, only.

JLV

[Ray.R]

I forgot to mention... Even with the dual monitors on the clone PC, I never get that message...

Don't give up the dual monitor... It's great with LV 🐵

[shoneill]

Hi Pawel,

Copying everything in one go from one block diagram into a new one normally copies all front-panel objects too (which arelinked to the block diagram) and maintains their positioning/formatting. I don't quite understand how this will take a lot of time. The sub-VIs don't neccessarily need to be copied, just the top-level VI I reckon....

Greets

Shane.

[pawel]

I have a lot of property nodes (direct) so all of them will change to indirect and I need to wire referencees to them. But you are right, even though it shall take some hours it is worth to try.

kind regards
Pawel