Insane Object Error - Image.cpp

[Will.D]

Is any other LV8.2 user having problems with customizing controls?

I have only needed to do this today since the upgrade to 8.2, and am having a hard time.  I have yet to come up with an exact method to reproduce this, but it's getting to be a big problem, as LV crashes about 60% of the time when I'm editing controls.

Is this a known issue?  I did some digging but didn't find anything specific to my problem.  I never had this problem with 7.1 (same hardware in my PC).

Message Edited by Day on 10-10-2006 04:04 PM

[mfitzsimons]

Typical method of correction this to copy all of you code from the VI having the issue, past it into a new VI, and save it.  This sometimes will clean up some bad connections.  Hope it helps but doesn't hurt to try.

[Will.D]

Matt, thanks for the reply.

Yeah, I have seen that as a solution.  Problem is that this wasn't just happening with the controls in one VI.  I will keep trying to come up with a way to reproduce this.  Knowing my luck I won't be able to.

[Justin D]

Day,

This was reported to R&D (# 42AG20IQ) for further investigation.  I've created a lot of custom controls and I've never had this happen to me.  Is there anything specific you are doing with these controls that you think might be behind this?  If we can reliably reproduce this then there's a better chance we can find a workaround for it.  Thanks for the feedback!

Justin D
Applications Engineer
National Instruments

[RavensFan]

I had a similar error message come up in the jump from LV 7.1 to LV 8.0.  It would cause a couple of hard crashes of Labview whenever I worked with one particular VI.  I found it was related to a wizard lock control that I had created in LV7.1 using the HMI Wizard options of my DSC module.  I actually had two such loops in my original program, one behaved, the other caused problems in the upgrade of the VI to LV 8.0.

I discovered this by creating multiple copies of the VI in LV 7.1 and deleting different block diagram elements from each and seeing which opened without error in 8.0 and which caused the problem until I finally discovered the problem piece of code.  It was really a divide and conquer technique.

I liked how LV 7.1 HMI wizard automatically created code that I could unlock and modify as I needed.  It seems that the HMI wizard was eliminated from the DSC module of LV 8.0 and 8.2. There were several other major changes in the behavior of the DSC module from 7.1 to 8.0 which I am still trying to learn.

If you can discover which control or what piece of code (hopefully it is only one) is causing the problem, perhaps you can delete it in the older file version, upgrade the VI, then recreate it in the newer version VI.

[Will.D]

Justin, thanks for the report!  I will post any more info I find in this thread.

I'm not sure it will be soon as I may get pulled into production next week.  Guess we'll see.

Ravens Fan, thanks for the info.  Like I said to Justin, I'll keep digging! 

[Travis_M.]

Also, when you restart LabVIEW and get that error dialogue, be sure you choose to 'investigate error' so that you can send us the error log file for investigation.  We only need one submission per error, but there is useful information in those files that we can use.

Thanks!