LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

many running of system exec.vi.

In my application (Two lakeshore335), system exec.vi was called in every 2 sec.

When I used "cmd /k", the memory of application is increased very rapidly (32bit, >1Gbyte and then shutdown).

Then I changed the option to "cmd /c" and the memory is minimized.

 

However, I found the application separately in other section (maybe "APP") of task manager in Windows 10.

In the section, the application showed some strange stuffs as shown in the following image.

(Note: 455 is a number which is increased as time goes on.)

When I terminated the application in task manager, application in the section and many "Windows Command Processor" were not killed automatically and I need to kill them separately.

 

In summary, "cmd /c" and "cmd /k" is the same problem in continuous runing.

 

In ideal case, I would like to use only one Windows Command Processor, which should be killed when the application was terminated.

 

How can I resolve this trouble?

 

YAHOO.PNG

0 Kudos
Message 1 of 2
(539 Views)

I changed "wait until completion" -> true, the trouble was disappeared.

 

labmaster.

Message 2 of 2
(502 Views)