Fatal Internal Error 0x89B93EF0 : image.app, line 4282 on OSX when opening any VI

[ElGalloGringo]

I had been trying the LabView 2015 demo, but because our school has access to LabView 2014, I switched back to using it. The first couple of times I ran LabView 2014, it worked great. However, now every time I try to open a VI or create a new VI I get the following error and crash:

"Fatal Internal Error 0x89B93EF0 : "image.cpp", line 4282

LabVIEW version 14.0"

Labview opens perfectly fine, but crashes every time I try to open or create a VI. I have attached the log file that was generated in the lvfailurelog directory. It seems it has something to do with drawing, but I have no clue how to fix it.

[sunaenae]

Hi ElGalloGringo,

I am looking into this issue and will get back to you under the service request you created via email. Thanks!

[turokg]

Hello

Would be greatful if you send me some info about this crash too.

Labview2015 evluation crashes in the same manner as the topic starter described. 

Macbook air 2014, OsX 10.10.5

Fatal Internal Error 0x89B93EF0 : "image.cpp", line 4282 LabVIEW version 15.0

[sunaenae]

 Hi turokg,

I found that the "image.cpp" error is often associated with an issue with a video driver. See the following post to see how to resolve an "image.cpp" error: http://digital.ni.com/public.nsf/allkb/01B186B5CEB1D07786256747000F4319.

It also looks like in Mac OS X Yosemite, this error could be fixed by connecting to an external monitor with the Thunderbolt cable. It seems that there is an error when the VI is being opened in a location outside of the primary screen (and where the external monitor should be when it does not exist).

If connecting a monitor does not work, more generic approaches such as updating your graphics card driver may also help. Adjusting graphics card settings, such as reducing screen resolution and disabling any "hardware acceleration" modes that your graphics card may have, could also be useful.

Unfortunately, LabVIEW for Mac 2015 is only compatible with OS X 10.10 and before, so the issue may not be addressed in your newer version of the OS, as extensive testing has not been conducted yet. The other customer was able to resolve their issue by updating their version of LabVIEW, but as you have the newest version, trying the aforementioned steps would be a good start. If the issue continues, please feel free to reach out or call or email our support system for more detailed help.

[ElGalloGringo]

I couldn't wait to have a working version of LabView for course teaching purposes. I saw that I could get a education license of 2015 through the university for cheap and it was worth my time to just upgrade to 2015. I haven't seen the problem since switching.