insane objects in front panel (fpsane.cpp line 435) destroyed my vi!

[Nathan West]

While working on a vi, I added a control on the block diagram by copying a block of code.  When I went to the front panel, the button was a million miles away from the rest of the controls (as it usually is).  So I hit select all and then pressed align right edges (an operation I have used many times in the past).  Well everything disappeared from the screen and the scrollbars moved to the right and bottom.  The vertical scrollbar can be moved up and down, but nothing shows on the screen.  The horizontal bar cannot be moved. and I cannot pan the screen horizontally by any means. When I close labview and reopen I get internal error fpsane.cpp line 435.

Is there any way to recover from such a crash? 

Of couse I saved the design before closing, hoping that it would come back, so now I have to go back to last night's backup and redo all of today's work!

Nathan

[DavidMaidman]

Hi Nathan,

I had a similar problem a while ago, specifically with a typedef control. I searched on this forum and there are lots of recomendations, however what I found worked was to disconnect the control from the typedef and then to resave. This let my VI save without an 'insane error'. I then used the right click>>replace>>.... to relink to the typedef control.

If your control is a typedef give it a try.

If it isn't I have also found dragging/dropping the block diagram code in to a new VI and resaving.

[Ben]

---

Nathan West wrote:

While working on a vi, I added a control on the block diagram by copying a block of code.  When I went to the front panel, the button was a million miles away from the rest of the controls (as it usually is).  So I hit select all and then pressed align right edges (an operation I have used many times in the past).  Well everything disappeared from the screen and the scrollbars moved to the right and bottom.  The vertical scrollbar can be moved up and down, but nothing shows on the screen.  The horizontal bar cannot be moved. and I cannot pan the screen horizontally by any means. When I close labview and reopen I get internal error fpsane.cpp line 435.

Is there any way to recover from such a crash? 

Of couse I saved the design before closing, hoping that it would come back, so now I have to go back to last night's backup and redo all of today's work!

Nathan

---

I have heard of issue with diagrams being too large (larger than 65,535 ? ) causing problems. NOt sure how to avoid it in the scenario you reported.

If this happened in LV 2009 you may want to check for the recent service pack that I believe had a fix for crashes with large diagrams.

Offering what I can,

Ben

[Nathan West]

Thanks for the quick reply. 

I am using LabView 9.0.  I will look into SP1 if that will solve the problem.

If it is not already addressed, I hope that NI will fix the way that new controls are added automatically.  They always appear far away from everything else and then I have to slowly drag them across empty space to get them back to my other controls.

Thanks,

Nathan

[Ben]

For faster dragging...

If you drag an opbject onto the screens scrollbar it goes faster.

If you select the object, scroll to the sane area then select another object in that area and doa "allign left/right"

I have not seen the controls going out into la-la land but I keep my diagrams small so maybe why I haven't seen it.

Ben

[macolit]

Hi everyone!

I have been having problems with our recent upgrade from LabView 7.1 to 9. I have removed 7.1 completely and have installed everything that came with the installation DVD's in LabView 9. When I went to my old VI's and continued to work on them, after I have saved the VI and exited LabView, Labview would still linger in the background and do nothing. This prevents me from opening LabView again. I then would have to go to Task Manager to terminate the process. As soon as I do this and re-open LabView, I would get the pop-up window asking to investigate the recent crash.

I am currently in contact with support@ni.com as well, but they have not solved the issue so far. This is why I am seeking help with the rest of the community. I am hoping that somebody out there knows anything about this issue. I am attaching the most recent lvfailurelog I have encountered. 

I have currently installed the most recent patch to LabView 9 and the only thing it's done is to illiminate the logging of the failure because it's no longer asking me to investigate after terminating the application from Task Manager.

Marcos