11-12-2010 06:29 AM
My application (Monitor Panel) is a LabVIEW 2009 SP1 built executable. Occasionally it crashes when exiting, throwing up the following Windows XP error dialog:
The crash doesn't always occur, perhaps one in every two or three sessions, but it is only when exiting the application.
The application appears to shut down perfectly smoothly (my panel disappears etc.)
The application calls one ActiveX component, which I'm fairly certain I close on exit.
The application opens two TCP connections to a cRIO device, and also creates two TCP listeners for incoming connections from other applications. I'm fairly certain I close all these on exit too.
The application uses Shared Variables (networked shared variables) for populating and making data available to bound front panel controls and other applications.
The application runs without a problem, I can't see any reason for it to cause a crash on exit.
Does anyone have any ideas as to why a LabVIEW application that appears to work perfectly might cause a Windows crash like this?
11-12-2010 08:00 AM
Further info:
This appears to be related to the ActiveX control I use. If I remove the ActiveX component from the application, it doesn't ever crash. If I leave it in, but don't use any subvis that require it, it still exits cleanly. But as soon as I call the ActiveX component, my application crashes on exit. And I'm pretty sure I'm closing the reference to it too!
Anyone else ever find this problem? I'm quite stuck on what to do
11-12-2010 09:18 AM
What activeX component are you using?
11-12-2010 09:38 AM
Hi RavensFan,
I'm using a 21CFRPart11 compliant SQL-based user permission rights database access tool (DataTrak), which is a legacy ActiveX control from this project's previous releases. Unfortunately the company that make it are long gone, but I'm stuck with it - no choice, no support.
I've been tracking the problem down, and although the problem only occurs when I call up the ActiveX component then exit, it also seems that the problem goes away if I remove my .NET marquee-style progress bar from a seperate subvi. Confusing, but the system is stable with one or the other, but exits with a crash when both are included the executable!
Given the ActiveX control is a requirement, and my marquee progress bar is a niceity, it looks like the progress bar will have to go...
11-15-2010 09:06 AM
Hi Thoric,
Have you tried looking at the Windows Error Log? (Found through right-clicking on my computer and selecting 'Manage') You may be able to find a specific error code which could give you an idea as to whats happening when the program has crashed.
Best regards,
Chris
11-15-2010 09:54 AM
Hi Chris,
Thanks for the suggestion. I've since taken out my .NET progress bar and all seems well, so I'm probably just going to leave it at that, rather than re-introduce it and see if I can diagnose the problem further. Although I'd taken a peek at the Windows Error Report that gets generated (no use whatsoever to me), I hadn't considered inspecting the Windows Error Log. Thanks for the suggestion