Jump to content
Sign in to follow this  
ppat

Program closed but remains in the process list

Recommended Posts

ppat

This is one of the weidest things I experienced: I have installed SyncBackSE as a portable app on my local disk. I run SyncBackSE with the command line directly (not through Autoit):

"M:\[myfolder]\SyncBackSE\SyncBackSE.exe"

When manually exiting the application SyncBackSE, its process goes away from the process list. This is fine.

BUUUUUT

When I laucnh if from AutoIt (v3.3.0.0) on Windows 2000 Professionnal SP4 with this instruction:

RunWait("M:\[myfolder]\SyncBackSE\SyncBackSE.exe")

and then manually exit the program, the process SyncBackSE.exe hangs in the process list. The RunWait can never go beyond the instruction and I am stuck, unless I manually kill the process.

Could someone from the dev team try to reproduce this issue, then tackle it?

Note: I tried with other software, I do not have this problem.

Share this post


Link to post
Share on other sites
Inverted

You should test it on a windows XP machine, to see if it's related to win2000 or that SyncBackSE program. I think it would help the devs a lot.

Edited by Inverted

Share this post


Link to post
Share on other sites
ppat

As stated, the problem I have is on Windows 2000 Pro SP4. Developpers should first reproduce the problem in the same environment, then check the root cause.

If this helps, XP is a totally different story, works OK for me.

Share this post


Link to post
Share on other sites
ppat

In the same Windows environment, I tried a script with AutoHotKey. My ahk file is

RunWait, "M:\[myfolder]\SyncBackSE\SyncBackSE.exe"

And this works, the SyncBackSE.exe process disappears from the process list after closing SyncBackSE.

This is not the case when SyncBackSE is launched from an AutoIt script. So there seems to be a problem with AutoIt.

Share this post


Link to post
Share on other sites
rudi

Hi.

As a work around, until the root of your issue is found:

What happens, when you "wrap" the prog launch into a CMD file?

#include <file.au3>

$SyncBackSE="M:\[myfolder]\SyncBackSE\SyncBackSE.exe"
$CMDfile=_TempFile(@TempDir,"Wrap-it-",".CMD",5)

filewriteline($CMDfile,"Start /w " & $SyncBackSE)
RunWait($CMDfile,@TempDir,@SW_SHOW)
MsgBox(0,"Exit done","CMD file exited fine",5)

FileDelete($CMDfile)

Regards, Rudi.


Earth is flat, pigs can fly, and Nuclear Power is SAFE!

Share this post


Link to post
Share on other sites
ppat

Thanks for your help. Actually, the problem is solved. I assume that it was the influence of a Firewall.msc file. I built that file to mimick a firewall, but it had many side effects, such as protecting the registry from change. Now I got rid of that file, and everything is in order now.

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
Sign in to follow this  

×

Important Information

We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.