Looks like no one’s replied in a while. To start the conversation again, simply ask a new question.

Force Quit - not working

What do you do when Force Quit will not Force Quit the application that is not responding? I have been just holding down the power button and shutting the computer down as I have no other choice in the matter. Sometime having to do this about three times in a row for an app...not to mention names Final Cut Express 4.

iMac Intel Core 2 Duo, Mac OS X (10.5), 2.1ghz, 2.5gb Ram, 20" iMac

Posted on Dec 9, 2007 10:09 AM

Reply
19 replies

Dec 17, 2007 8:47 PM in response to macjack

still not working here. i had to reboot my computer, not good.

thats the biggest thing for me about mac os 10.5
in 10.4 the force quit was brilliant, always working in the second you asked for it. now the force quit look like the Windows Xp thing. That really bug me. Really not efficient.

i hope people at Apple see it and solve that issue on the next update.

Jan 9, 2008 2:55 PM in response to Freis1968

I can force quit to a point, but it doesn't complete the job. Most times it will close the application, but it remains in my dock as active. If I attempt to open the application again, I get an error.

Can I just say that I've had more problems since I've loaded Leopard than I ever have had on a Mac (15 years). I've been on the phone for hours with Apple Tech and they have yet to fix a problem. These posts rarely solve anything either.

Sorry. Just really getting frustrated.

Jan 25, 2008 12:44 PM in response to Freis1968

I also have found Leopard's force quit to be slower, maybe less effective - with hung processes. (It works great for processes which aren't locked up.) Still, I have yet to meet a hung process that force quit (or multiple force quits) couldn't kill EVENTUALLY. I usually end up using force quit from (1) the Apple Menu, (2) Activity Monitor, (3) the Dock. Or all three. Repeatedly. And then wait.

I wonder if the direct approach - Unix "kill" command - is more effective. That would be interesting to test.

I wonder if this new behavior is related to the "spindump" process. You know, the one that pops up in the Console with the amusingly ominous message "Process xxx is being monitored." whenever an application hangs up. Is this new to Leopard? If so, its attempts to keep an eye on the potentially dying process may be interfering? Just a crazy speculation.

I gotta say that, overall, Leopard has been the best Mac OS for me ever (20 years). Sorry, couldn't resist.

charlie

Feb 26, 2008 3:13 PM in response to dj2008

Actually there is something really screwy about Leopard (10.5.2) ...

I've got a nasty Parallels virtual hung, so I:
* quit it
* force quit it from it's taskbar menu
* Apple menu force quit it many times.
* Activity monitor does not show it running, but the task bar does.
* Relaunch Finder, no change
* sudo su [password] just to make sure
* Open a terminal, ps aux and there's a process in the list (Parallels) with zeros all the way across it
* kill -9 [its process number]
* Kill comes back with no complaints, but the process is still there.
* repeat several times as both root (su) and [me] - no change at all.

I have never, ever seen a *nix process survive a kill -9 ... Leopard is starting to look more Vista-ish all the time and it's REALLY getting bothersome. ::sigh:: I miss Tiger something fierce...

Force Quit - not working

Welcome to Apple Support Community
A forum where Apple customers help each other with their products. Get started with your Apple ID.