I've got an AppleScript that I usually launch out of Quicksilver, but occasionally, the script hangs, never exiting. (I think it's waiting on a non-existent window to appear).

This results in Quicksilver being monopolized, waiting for the script to die off.

If this were a Windows box, there would be a "scripting host" process I could end to fix this, but I'm not sure if OS X has a similar process. Nothing jumps out at me in the process list.

Of course, I could just kill and restart Quicksilver, but I'm wondering if there's an explicit way to just kill a runaway applescript that's running in the context of another application?

  • is the applescript an app? If so, yes, you can kill it separately. It will appear in Force Quit [Cmd/Opt/Esc] idk if it isn't an app. – Tetsujin Jan 9 '15 at 17:14
  • Negative - it's just a script. If it were an app running in its own process, this doesn't happen. – Mikey T.K. Jan 9 '15 at 17:17
  • 1
    How exactly is Quicksilver launching the process? Does it call a shell script that lets the OS handle things independently or is it simply another thread in the Quicksilver app? I've never seen this, but I use LaunchBar to launch things so there may be an architectural difference at play. – bmike Jan 9 '15 at 17:26

It looks like the AppleScript is run within Quicksilver’s process (depending on how you run it). If that’s the case, you’d need to relaunch Quicksilver. If it’s not completely frozen, you can do this quickly with ⌃⌘Q.

It might also be possible to set some kind of timeout in the script to prevent it from hanging indefinitely.

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .