Insane Object Error - Image.cpp

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
Attachments:
Insane Object Error - image.jpg ‏16 KB

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.

Similar Messages

Fatal Internal Error: "image.cpp", line 13192 when trying to insert a cursor to graph

NOTE: This IS a duplicate post from the Breakpoint. Text slightly changed. The post in Breakpoint can be deleted. All comments should be placed in this thread.
I resolved the "Fatal Internal Error: "image.cpp", line 13192 when trying to insert a cursor to graph", but would like to share to find out if others have seen this and to determine whether this is a bug, or if it's time to redo my PC, or buy a new one..
I have an existing graphs (qt 6) which originally had 2 cursors. This occurred while trying to add the third cursor.
Up until attempting to add the last cursor, the program worked great, and I had been running tests for a while. However, I do recall seeing this problem when creating the original cursors, but not to this extent. Plus I don't remember the original error message from that time.
I needed to add one more cursor to the existing graphs. As soon as I add a new cursor and set it's properties, I get a nasty error message and without warning LV8.2 simply closes itself (well, the only warning was the error message. Tried it 3 times, same result.
Here are the steps:
Shut down the PC, went for a coffee, rebooted the PC. Opened the LV project, opened the VI. Immediately went to the graph properties to add the new cursor by doing the following steps:
Right click graph indicator icon on block diagram.
Select Properties.
Click on cursor tab.
Click on Add
Select Cursor 2 (3rd one, newly created)
Change color
Select cursor as a line
Remove checkmark for "show cursor"
Click OK
I need to do this to 3 other graphs, same steps. And as soon as I get to the step before clicking OK, I get the error message.
I managed to get an additional one done, by immediately saving after each step (yep going in & out of the properties). But I've had this problem before when creating the first two cursors.
Is it a bug? Anyone else seen this? Using LV8.2. And the message is right about LOOSING ALL unsaved work!!!!
Here are more observations:
Tried creating a new one on the second graph. As soon as I clicked on the color, it crashed!
See the error explanation below. It is really clear, now anyone can solve it    LOL!!... According to the error log, there's a bad image out there
.\manager\image.cpp(13192) : DAbort: bad image in ValidateImage
$Id: //labview/branches/Europa/dev/source/manager/image.cpp#47 $
0x007A81E8 - LabVIEW <unknown> + 0
0x007A7BDB - LabVIEW <unknown> + 0
0x00829D74 - LabVIEW <unknown> + 0
0x008546CD - LabVIEW <unknown> + 0
0x00C054E6 - LabVIEW <unknown> + 0
0x0081B9C8 - LabVIEW <unknown> + 0
0x0081EB9A - LabVIEW <unknown> + 0
0x0084D9D4 - LabVIEW <unknown> + 0
0x00854663 - LabVIEW <unknown> + 0
0x00C054E6 - LabVIEW <unknown> + 0
0x0085F7A1 - LabVIEW <unknown> + 0
0x00BBACDD - LabVIEW <unknown> + 0
0x00C06A2F - LabVIEW <unknown> + 0
0x0085AA46 - LabVIEW <unknown> + 0
0x00C06A2F - LabVIEW <unknown> + 0
I observed the title bar after making changes to the properties. I noticed that 3 out of 4 times, while changing the properties of the graphs to include the cursor, and saving after each & every step, that there were no stars appearing on the title bar to indicate "unsaved changes". Saving was also much slower than usual. I suspect, the program never got to placing the star before saving occurred. However, I am noting everything.
After creating the cursors, saving was and is normal, and the program runs well..   I have run tests without problems.
Does anyone have a clue at what causes this? Has anyone seen this before?
Thanks,
RayR

Hi Donovan,
I can't remember seeing this elsewhere. When I get a chance, I'll create a new (blank) vi with new graphs and will repeat the steps.
I will let you know if I see this in the new vi.
Thanks!
RayR

Stop labview application from MS VC got internal error: image.cpp line 11450

Hi:
I need to control a labview application (It's been compiled as exe file)from my MS VC program. I tried using PostMessage(hWnd, WM_CLOSE) from whithin my program as MSDN suggested method to stop an application
cleanly. However, when i put my program in debugging mode and run it step by step, the LV program generate an internal error "image.cpp linexxxx" after it reached that PostMessage() call. in run mode , the Labview app simply ignore the WM_CLOSE message sent from my program.
So is there any other ways to stop labview application from VC program?
Thank you!
ls

> So is there any other ways to stop labview application from VC
> program?
You can use ActiveX. Turn the server on for your built app, open a
connection from VC, and use the app or VI properties to get LV to exit.
Greg McKaskle

How do I fix an "Insane Object" Error ?

I am receiving an "Insane Object" error when I load one partuclar VI. Is there any way to "copy" the diagram to a new file to fix the corrupted Object ? I am using Win N/T 4.0 and LabView 6i. The module was originally designed using LabView 5.X and the Module appears to work OK after accepting the Error Messages.

I think the most complete discussion of this situation can be found in the NI KnowledgeBase. Just go to the main ni.com site, search for "insane object" and follow the first hit.
That KnowledgeBase entry was created with a lot of input from some of the LabVIEW developers, so it's a pretty good guide.
Regards,
John Lum
National Instruments

Insane object error does not resolve upon re-load

http://digital.ni.com/public.nsf/allkb/AFA28DCC3DE89839862566B200594E8C
does not resolve this issue. Even when I close the VI & re-open it, I get the following error message:
I tried doing dozens of undo edits of the last 10 or 20 changes. None of them work. None of the suggested fixes work at all, either.
Worse yet, I can tell that my code is not what is looks like. It is not running the code that is on the diagram, it is running some previous version of the code.
Solved!
Go to Solution.
Attachments:
insane object error.PNG ‏12 KB

Hi Greg,
Thanks for your reply. It sounds like you've been on both ends of a serious error/crash resulting in code loss before.
As Murphy's Law would have it, it happened right before quitting time.
I decided to stick it out & make it a late night while I remembered most of my changes.
I quit & restarted LabVIEW, pulled the VI from a backup done the day before, opened up the backup version of the VI, opened up the bad code, and tried pasting changes in. However, I soon got oodles of "insane object" errors, and gave up on this route.
I quit & restarted LV, opened up the backed up VI, opened the bad new VI on a 2nd monitor (after configuring the display etc.), and manually re-drew (i.e., "re-wrote") all my code just by inspection.
This worked. (To play it safe, I also forced a system backup before going home, and saved lots of revs. along the way during my edits.)
I rarely have experienced "insane object" errors in my 10+ years of LabVIEW programming. Therefore, I have used little of other languages the past 10 years, and have developed so much re-usable code that I know well, I don't want to move away from it. It is quite unsettling / scary when it happens, especially on a large program. It makes me consider going back to text-based programming, where at least there's some inspection of all but the most messed up files (vim/binary mode, for example).
Anyway, I am on my way now, but will be even more diligent about "Save As" to save interim versions during long code writing sessions.
Also, I ran chkdsk per Apps Engr suggestion on a ticket I did later open after doing this post.
Thanks, Matt

The eig() instruction in my matlab script is causing an insane object error

I have matlab script in a vi that I want to use to calculate eigenvectors and eigenvalues of a large array. I started with a small array (3x3)and it calculated them incorrectly. However when i ran the same script in Matlab the correct values are returned. On top of that when I try and save the vi after running it I get an insane object error at FPHP+DC. I tried rewriting the vi without copying and pasting etc. but it wont go away. I then simplified the vi to simple integer addition and removed the eig()instruction and error doesn't appear anymore, so it seems that the eig() instruction is causing all of this and it isn't even giving the correct answers! Where does this leave me? I can't get the e
igenvectors using the Labview vi because the array i will using eventually is (944x944) and the labview vi gives me an error saying I have exceeded maximum iterations. This is why I am using Matlab in the first place.
Thanking you in advance!!
Marion

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.

Insane object error(The string control not getting any values)

In LabVIEW 8.2 i am using the string control to get the text from the users, and initially there was no problem at the time of development it works perfectly, after building the installer,
these string controls are not getting any string input, it seems like a disabled one, but actually it was not disabled, when we try to click over that through the mouse,
that text inputting cursor was not blinking over there,I screen looks as below, some error messages are thrown from the LabVIEW like insane object error, even
now there was the same problem in the source code itself, what to do rectify this. Only this part generates error all other remaining screen panels are working perfectly.

This kind of problem can be a pain to locate. This often occurs when the wiring to or from a control or indicator is bery long, convoluted and hidden inside of structures or behind things. So first, you need to identify which VI specifically is generating the error by individually saving VIs and subVIs until you find the one that is generating the error. Now try and remember the last time that VI saved without a problem and what edits you made since then. Places where I have had this occur was when I drag-copied a control and a couple VIs into a small structure. Sometimes the wires would seem to conect up properly, but when I tried to save the VI I got this error. The solution was to disconnect all the wires associated with the VIs I had copied and rewire them.
Also, can you post the VI that is doing it? Shouldn't need the subVIs for this...
Mike...
Certified Professional Instructor
Certified LabVIEW Architect
LabVIEW Champion
"... after all, He's not a tame lion..."
Be thinking ahead and mark your dance card for NI Week 2015 now: TS 6139 - Object Oriented First Steps

Insane Object errors

I'm suddenly getting a lot of insane object errors on my program, I've tried everything listed in the Knowledgebase topic. They're only wire and sgnl graphical errors, but they aren't resolving themselves. When I change constants in the program, more insane objects pop up.
It's a little bit frightening, please help.
-Capuchin

Hi Capuchin,
As you probably are aware from reading through that KB, insane objects mean your VI has become corrupt and you may need to rewrite your code.
I have some debugging tools I can use to try and debug this for you. Could you post your code please?
I also have the email you sent to UKSupport so I can contact you directly by email if you would prefer.
Kind regards,
Sarah
Applications Engineer | National Instruments | UK & Ireland

Insane object error causes LabVIEW 6.0.2 to quit (crash)

When I made a small modification of the wiring diagram and try to save the vi, the insane object error comes up and trashed all the modification. If I restart LabVIEW and apply the same modification, I can usually save the vi without problem. But next time when a new modification is made, LabVIEW would crash again when I try to save the vi. I am running LabVIEW 6.0.2 under Windows 2000.

I have seen the same error as well. It has occured during edit sessions (attempts) on very large (complicated) diagrams when my video settings were at 1600x1200. I have discovered that the errors seem to be related to the video resolution settings AND the size of the block diagram. I have a Gateway twin-cpu workstation with a 1x AGP video card with 16MB of RAM; however, the problem only occurs at high resolution settings. If I set the video to 1024x768, the errors stop occuring. For those applications that require high-res settings, I code at low resolution, close the diagram, change to high resolution, and can work on the front panel with no problems.
PS...
I was able to freeze the screen during one of the failures and found that all of the objects were literal
ly extruded to the same heigth as the wires -- it was really bizarre! The computer was "locked up" so that a screen shot was not possible. I called NI tech support and was told it was a "most likely" a video card problem.

I can't fix my insane object error!

Hi all,
I'm getting the following error messages when I try to save my VI after running it:
Insane object at FPHP+208BC in "backup.vi":{sub}(0x10): Scale (DDO)
" " FPHP+20634 " " Waveform Chart (DDO)
" " FPHP+20E78 " " Scale (DDO)
" " FPHP+20CB0 " " Waveform Chart (DDO)
I read all of the info on insane objects available on the web site, and followed the instructions to fix the problem when it first appeared last week. I deleted and recreated the last charts and scales that I made, and eventually I recreated every chart and scale. This seemed to fix the problem, as I had no more error messages...until this morning.
I'd like to avoid having to recreate everything all over
again if possible. It's probably best that I send the VI to someone to take a look at and try to fix. We're using an opto22 interface for our readings, if that helps at all. Hopefully someone can help me fix this problem....
Thanks,
Andrew Poyton
McMaster University
Hamilton, Ont.

Andrew,
I was having a very similar error this morning. It turns out that the source of my problem was the range on the y-axis on one of my waveform charts was messed up. I had it set to autoscale and had been running the program and it plotted some really huge numbers because of a calculation error in one of my formulas. In any case, it seemed to run fine despite plotting bogus information, but when I went in to make changes and then tried to save I received the error messages similar to your situation and could not save. I fixed it as follows: I simply changed the values on the upper and lower end of the y-axis to something reasonable like +10 and -10. Then I tried to save and it worked just fine.
So you might take a good look at your waveform plots and check
the values on all of the ranges. I hope that helps you.
tony

Insane Object error while saving: Can i identify case from error message?

Hi,
I get the following message "Insane Object at BDHP+36C8c in "Data Logger.vi"{graphics}(0x80):Wire Segment (WIRE). I have seen errors like this in the past. It usually happens when the wire gets coiled like a snake or gets behind a place that cannot be viewed etc. The last time i had the problem, i had to delete the wire and rewire to have the problem solved. Is there any way for me to identify the case that has this wiring problem from the error description? I get this annoying dialog everytime i save my vi. Thanks for your time in advace.
Anand.

The message means there is a problem with an object on the block diagram (the BD of BDHP). Fixes include copying the diagram to a new VI, and randomly deleting objects and replacing them. You might also try pressing control-shift-run arrow on the VI to perform a binary recompile of the VI. It is a long shot but it is quick and easy do do. Ususally you will not see anything happen but occasionally LabVIEW can highlight the error or even correct it.

Internal fatal error: image.cpp

Hi all
For a couple of times this week (it was the first 2 times that this error occours) it appeared the error that you can see in the attached pic. I was watching a pretty large block diagram surfing it with the navigation window. I clicked several times the block diagram and the navigation window in order to adjust my view, when suddenly that error appeared. Then LV shut down. I launched the program again and it was all right. What was it? Some ideas? I don't want some critical error in my LV: i mean, i'm not talking about windows
Kind regards
I love the smell of napalm in the morning
Attachments:
errore fatale LV.jpg ‏71 KB

This problem has been fixed in Labview 8.1. So i suggest you to upgrade (Labview 8.2 is the last version).
If you want a work-around to the problem, here you have two possibilities:
Hide the front panel before allowing the application to exit. You can do this by creating a property node for the VI and writing 'Hidden', or 'Minimized' to the FP.State property. If your activation of LabVIEW has event structures, you can place this code inside the This VI->Panel Close event. If you do not have event structures, you should disable the close glyph on the window border and implement the above code following your main application code.
Convert your application back to a previous version of LabVIEW (such as version 7.0 or 7.1) which is not affected by this error.
Ciao!

Getting error "image.cpp" line 8723

I tried to import pics in my window panel, but I alway's get this error!!
What can I do!!!!
Thanks to all of you
Sebas

I should see your vi.
Anyway that sounds like an internal error.
Visit the page:
www.ni.com/support/failure/commerr.htm

Internal Error : "image.cpp", line 13334

I receive this message when I start Labview 8.5. It also says to relaunch Labview or contact NI to resolve the problem.
WHAT IS THE PROBLEM??????????

I'm sorry for the issue you had with customer service yesterday. I would like to inform you can purchase LabVIEW Standard Service Program and have access to over 100 Applications Engineers who specialize in every major NI Product Catagory.
LabVIEW Standard Service Program (SSP)
Standard Service for LabVIEW
Automatic upgrades and updates, free of charge
Access to NI Applications Engineers one-to-one via phone and e-mail for technical support
Exclusive access to free, on-demand training modules in the Service Resource Center
Mark
LabVIEW R&D

Image.cpp error line 11035, LabVIEW 6.0

I recieved the error image.cpp, line 11035 and cannot find the patch to fix this error. The program shuts down when I try to print. Where do I find the correct patch for this error in Windows?
Thank you.

Hi, I believe that this problem was solved with patch 6.02 see: release notes for 6.02
Hope that this helps,
Erik van Dijk

Insane Object Error - Image.cpp

Similar Messages

Maybe you are looking for