Exit Labview.vi causes crash.

[RBrown]

At the end of all of my programs I put the Exit Labview.vi to close the application.  Up until Labview 2010 I had no issues.  Now every time the vi is run at the end of my programs I get a Windows error with no information, just a Microsoft send error report screen.  I debugged deeper and I found an unhandled exception in ntdll.dll Access Violation.  Does anybody else have a problem with Exit Labview.vi?

[altenbach]

I assume you are talking about "quit LabVIEW", the one with the text "exit" on the icon. 😄

I use it in my applications and don't have any problems.

What is your OS?

Is this in LaVIEW 2010 or 2010 SP1?

[smercurio_fc]

What is your code doing? Have you tried using the function in a simple VI? It sounds like your VI is not properly cleaning up certain resources. Are you using any hardware drivers?

We await further enlightenment....

[RBrown]

2010 SP1 on multiple XP Machines.  I close everything that I open, however that might not be the case with Labview.  I just hate that the applications worked fine in 8.6 and all I did was upgrade.  Now I get errors.

[smercurio_fc]

Well, until you give us more details, we can only guess. How about throwing us a bone?

[JtotheB]

Hey RBrown,

ntdll errors are non-specific and might be caused by anything. Are you getting any error messages or crash reports when you restart LabVIEW?

[RBrown]

Labview does not give me any errors or messages.

My program talks to 10 instruments on serial ports, a USB-8451, a PC scope, a JTAG programmer and in I2C adapter.  All of which I close out before I end the program.  Again I never got an error using 8.6.  So what changed?

[falkpl]

Does the application use any dlls (ie 3rd party drivers wrapped inside of a vi).  The way 2010 handles dll calls can actually cause problems that were automatically handled in the past (ie wrong call type).  Do you pass error wires throgh out your code to catch errors that are generated?

[RBrown]

Yes to both.

[rolfk]

Then it's time to look at those DLL calls. There might have been errors in them already but for some reasons it may have not shown before you upgraded. I would start with the non-NI hardware drivers by disabling any access to them one by one. See when the error stops. Then you have the culprit and need to look closer into that driver. If it is an NI driver, try to update to the latest version. If it is a 3rd party driver try to find if they have updates and otherwise it is debugging time, looking at every function prototype and trying to see if it matches what the Call Library Node implements.