Another LabVIEW Crash

[NIJanell]

Hello Stefan,

Can you post your error log file and a small version of your application that still creates the error?  This is information that I would like to add to the report I previously sent to R&D.  I will need to reproduce the error internally, which we could not previously do.

Thanks!

Janell R | applications engineer

[StefanW]

Hello Janell,

Here comes the error log. Unfortunately we were not able to reproduce the error in a small application. (Our Application has about 1500 VIs). But it is reproducable, that it happens with LV 8.20 and 8.21 every time closing LV after the application has closed. With LV 8.0 and 8.01 everything is fine. If there is no other way to stop the error pop-up, perhaps we will use taskkill for the EXE.

[NIJanell]

Hello Stefan,

Although you are getting a similar cpp error, the stack in the log file seems to be very different from the others located in my previous report to R&D.  Do you get this error when you run the code in the development environment?  Have you tried doing a binary search (delete half the code, see if the error occurs, repeat) to narrow down the location of the problem?  We really need to be able to reproduce this in house to effectively troubleshoot and fix this error, but it will be near impossible to upload the application in its current state. 

When the error occurs, do you choose to investigate now and submit the error log file to NI?  If not, I would highly suggest that.

Janell R

[StefanW]

Hello Janell,

I was able to reproduce the error accidently - be recycling parts of the code. It was a programming mistake (not closing a notifier reference) but this shouldn't lead to a fatal.cpp.

Create a smart global with two cases, one for "set" where you use obtain notifier and "get" where the shift register is wired to the output. Set execution type to subroutine and place the global in a new VI. Run it once with "set" and close LV - the error should appear.

[AdnanZ]

Hi Stefan,

When your LabVIEW program crashes next, it should give you the option of choosing to investigate now or submitting the error log file to NI. Be sure to choose the option of submitting the log file to NI and give a description of the steps you took which lead to the crash. After that, an engineer will get in touch with you and you can discuss your code and behavior with him/her. That should be the best and fastest way to resolve this issue you are facing.