network streams avoid LabVIEW executables to close properly

[christian_w]

If I build an application that contains network streams operations, the application process will not be closed after the application stops. This happens even if I use the Quit LabVIEW call !

To examine this I used a simple add function with and without a sequenced  'Create network stream reader endpoint' call. The executable with a network stream call, stays in the process list after stopping the application.

It doesn't matter that the pure create stream call is incomplete to create a stream and is in this way without any functionality. Due to a timeout error no stream will be created, but it ends as described. So this scenario is only to show the behaviour of the executable.

Any ideas ?

Thanks in advance

Christian

[christian_w]

For anyone who is interested I attached a sample project. I think this is a bug without workaround.

[christian_w]

Sorry I forgot the configuration

LabVIEW 2010 f4

Windows XP SP3 up to date patched

The executable build and failed to close in XP, will be closed correctly under Windows 7 ( tested with 64bit under runtime conditions )

Christian

[Jaypi]

We already encountered the same problem.

The only way to shut down the "zombie" executable is to open the windows task manager
(STRG+ALT+DEL)--> Task-Manger and then kill the application manually in the process list.

Best Regards

J.P. Oswald

[UM · Accepted solution]

Hello,

this is a knowing issue and is already reported to R&D with the

"Corrective Action Request 254821 - Executable with Network Streams leaves Process running in Task Manager in Windows XP".

This issue will be fixed with LV 2010 SP1

Regards
Ulrich
AE Specialist – NI-CER

[StefanA]

LabVIEW 2010 SP1 will be officially released on Febuary 21st.

Stefan