LabVIEW crashes while documenting a control

[Bob Schneider]

So, I've seen this error a few times randomly in the past few months, but this morning it has just gotten ridiculous.

I get a fpsane crash while trying to document a control.  Pretty much any control.  It's not consistent for the same control or same type.  But basically I'll go to create a new control, edit the label, caption, if it's an enum I'll edit items, and then I get to the documentation tab.  I figure hey, good idea to throw a few words in there about what this control is, right?  Well, LabVIEW ends up crashing sometimes while on this tab.  It happens when I'm typing things into the field, or if I'm just sitting there for a minute.  I had this error on 8.5 and hoped that maybe it got fixed in the background for 8.5.1.  Unfortunately not.

I was thinking maybe it was just the laptop I'm on, that somehow LabVIEW got corrupted.  But a colleague had it happen to him last week DURING his CLD test on a completely different computer than my laptop obviously.

Attached is the error message I received.

Was wanting to see if anyone else has had this problem at all.

[JeffOverton]

Looks like it might be a corrupted front panel

edit - http://zone.ni.com/devzone/cda/tut/p/id/6449#52297/4AIFC0R0%20by%20Category

could also be locking an already locked tab or using the enum property node RingText.Text

Message Edited by JeffOverton on 05-02-2008 11:09 AM

[Eriquito]

Hi Bob,

I apologize for any inconvenience this has been causing you.

It does sound like front panel corruption is one possibility.  Have you noticed this problem occuring in other vis as well?

Several issues related to "fsane.cpp", line 367 have already been reported to R&D, and we are working diligently to make the file more robust in future releases of LabVIEW.

Of course, once we've fixed the issues that have already been reported, we'd like to be able to test for your issue to make sure that has been fixed as well.  If you could post any more information (such as a log file or a vi that will help reproduce the error), I will add this information to the Corrective Action Request to make sure it is not overlooked.

Also, you can reopen your error log in LabVIEW by selecting Help » Investigate Internal Error... and then you can select Investigate and email NI directly, if you prefer.

Also, you may want to take a look around the forums for other workarounds that people have found:
    
LabVIEW Forum Post: error line 367