Thanks!
LiveCode Zombie Processes
Moderators: FourthWorld, heatherlaine, Klaus, kevinmiller
LiveCode Zombie Processes
I am having an issue that when I quit LC, the application quits but the LC process stays active (as reported by the Windows Task Manager). The next time I attempt to open LC, a second zombie LC process appears but not the application. I have to go into Task Manager, end the LC processes manually, then I can restart LC. Has anyone else seen this? I am not certain it is pilot error but might be 
Thanks!
Thanks!
Walt Brown
Omnis traductor traditor
Omnis traductor traditor
Re: LiveCode Zombie Processes
That usually happens when you have a message pending when LC closes. see pendingMessages in the dictionary
Re: LiveCode Zombie Processes
..........
Last edited by [-hh] on Wed Aug 13, 2014 3:34 pm, edited 1 time in total.
shiftLock happens
Re: LiveCode Zombie Processes
LC will not quit until all open processes are closed or completed. This includes pending messages, but also any open drivers (revSpeak, for example, opens a driver,) or any open sockets (libURL calls, or sockets you have opened in a script) or any handlers that have not yet finished executing. The stack should have a shutdown handler that closes everything it's opened and removes all pending messages from the queue.
Jacqueline Landman Gay | jacque at hyperactivesw dot com
HyperActive Software | http://www.hyperactivesw.com
HyperActive Software | http://www.hyperactivesw.com
Re: LiveCode Zombie Processes
Thanks. It happens even if I don't do anything, so it may be the annoying, always pending LC toolbar message "There is an updated version". That happens very frequently, as I (and I imagine others) use various versions on the same machine. I turned off all the "Notify me" boxes in Edit->Preferences->Updates and will see what happens.
Walt Brown
Omnis traductor traditor
Omnis traductor traditor
Re: LiveCode Zombie Processes
Hi Walt,
After I install a new version of LiveCode, I change the name of .setup.exe to _setup.exe. This prevents the updater from starting and keeps zombie processes away.
Obviously, this doesn't apply to standalones. For standalones, you need to make sure that everything finishes before quitting the app. You can do this with a script like this:
Kind regards,
Mark
After I install a new version of LiveCode, I change the name of .setup.exe to _setup.exe. This prevents the updater from starting and keeps zombie processes away.
Obviously, this doesn't apply to standalones. For standalones, you need to make sure that everything finishes before quitting the app. You can do this with a script like this:
Code: Select all
on quitMyProject
lock messages
-- stop using stacks
put the stacksInUse into myStacks
repeat for each line myStack in myStacks
stop using stack myStack
end repeat
-- stacks
put the openStacks into myStacks
put "message box,home,tool,Message Box,revTools,revMenubar" & comma & the short name of me into myDontClose
repeat for each line myStack in myStacks
if myStack is not among the items of myDontClose then close stack myStack
end repeat
-- messages
put the pendingmessages into myMsgs
repeat for each line myMsg in myMsgs
cancel item 1 of myMsg
end repeat
set the backdrop to none
// close me
if the environment is not "development" then
quit
end if
end quitMyProjectMark
The biggest LiveCode group on Facebook: https://www.facebook.com/groups/livecode.developers
The book "Programming LiveCode for the Real Beginner"! Get it here! http://tinyurl.com/book-livecode
The book "Programming LiveCode for the Real Beginner"! Get it here! http://tinyurl.com/book-livecode
Re: LiveCode Zombie Processes
Good idea, Mark, thanks, I hadn't thought of that.
Walt
Walt
Walt Brown
Omnis traductor traditor
Omnis traductor traditor

