LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

Fatal Internal Error 0x536B9E47

LabVIEW crashed with:

 

Fatal Internal Error 0x536B9E47 : "Cosmetic.cpp", line 576

LabVIEW version 15.0f1

 

This happened after I tried to wire a class indicator from one sub-VI method to the class control in another sub-VI method (same class).

 

A description of Cosmetic.cpp line 576 would be appreciated.

0 Kudos
Message 1 of 4
(2,785 Views)
That message means, "LabVIEW fall down. Go BOOM!"

...and that's all the detail there is to be had. Those sorts of messages are from our viewpoint, useless. If it happens repeatedly you can try calling NI, but that is likely to be an exercise in futility because they don't know what the message means either!

Mike...

Certified Professional Instructor
Certified LabVIEW Architect
LabVIEW Champion

"... after all, He's not a tame lion..."

For help with grief and grieving.
Message 2 of 4
(2,746 Views)

LabVIEW seems to be the only one at that party.

0 Kudos
Message 3 of 4
(2,715 Views)

Did you get the "We are sorry for the inconvenience" message?  So refined!

 

In LabVIEW 2011 (I think it was), I was doing things with Network Streams.  I had a VI that was perfectly fine.  If I edited it and moved a control (without changing any wiring), "We are sorry for the inconvenience".  

 

I did manage to find a workaround (I don't recall quite what -- I think I may have wrapped another structure around it).  At the next NI Week, I went to a talk on Network Streams, and after the talk, asked the presenter about my "bug".  "Oh," she said, "you're the one who reported that!  We fixed it ..." and, indeed, they had.  Been happily using Network Streams ever since.

 

Bob Schor

0 Kudos
Message 4 of 4
(2,697 Views)