As tremendous as macOS is at multi-tasking and control an incredibly huge number of open applications at any specified time, at the end of the day, they are machines, too, and are inclined to a machine’s restrictions. Until you barely ever use your Mac for heavy tasks, you must run into a frozen Mac, in any case once. I see you nodding your head in frustration over the statistic that your Mac is not as all powerful as you possibly assumed it to be.

However, I’m not here to make negative on Mac, I actually love Mac OS how well rounded the device and its OS is. I’m here to give you answer to your problem. Actually, scratch that, I’m here to give you two solutions. So, get pumped, and read on!

Force Quit Non Responding Apps on Mac: The Terminal Way

The Terminal – hands down the most useful app on the Mac, or any Linux, Unix, or Unix-like system. It basically gives you super-powers to control your computer, and it can do everything that you can do through the (really sweet and awesome looking) Graphical User Interface on your Mac. The thing with using the Terminal to force quit (or, in the Terminal language, “kill”) a non-responsive app, is that you need to know the “Process ID” (also known as PID) for the app that you need to kill.

The steps you will have to take, in order to find out the PID of a process are outlined below:

• Launch Terminal and type the following command:

ps aux | grep "process_name"

• This will list out some details about the process that matches the provided“process_name”. The second column in the details will be the PID of the process.

Note: The command will (usually) return two matches, but you need to use the PID value given in the first row.

• In my example, I’m trying to kill“Quip”,so I will use the PID value in the first row, which is “1676”.
• To kill the app using its PID, use the following command,replacing the “pid” with the PID of the app you want to kill:

kill -9 pid

• In our illustration, Quip has the PID 1676, so the command becomes:

kill -9 1676

Once you have executed the aforementioned command, the app will be force quit.

Force Quit Non Responding Apps on Mac: The GUI Way

Using the Dedicated Force Quit Menu

Not everyone is comfortable with using the Terminal, and to be honest, using the Terminal to kill an app takes a lot more effort than simply using the GUI. You don’t need to worry about the PID of processes to force quit them using the GUI. The steps to force quit an app using the GUI are illustrated below:

• Click on the“Apple”icon on the left corner of the menu bar and from the context-menu that drops down, click on “Force Quit”.

• Select the appthat you want to Force Quit, and click on “Force Quit”.

• You will beprompted with an alert, asking if you want to force quit the app; click on the button that says “Force Quit“.

Note: The Force Quit menu can also be launched by pressing “Command + Option + Escape“.

Using the Dock

It is also possible to force quit an app from the Dock. Every app that is open on your Mac displays its icon in the Dock, and force quitting an app from the Dock is even easier than using the dedicated Force Quit Menu.

1. Simply perform a two finger tapon the icon for the app that you want to kill. This will bring up a context-menu for the app, and you will see a“Quit” option.

Note: If the app is frozen, the option will be “Force Quit” by default.

2. While the context-menu is open, press“Option”,and the option that read “Quit” will now read “Force Quit”.

3. Simply, click on“Force Quit”to quit the app.

Don’t Let Frozen Apps Hinder Your Workflow on Mac

Frozen apps are both an annoyance, and a wrench in the works of the well oiled machinery that is your Mac. While it’s usually a good idea to allow apps some time to possibly unfreeze on their own, sometimes it’s obvious that the app won’t respond again, making force quitting it a necessity. If some apps on your Mac freeze again, you can now easily force quit them, and have your Mac working perfectly well. Also, there might be situations where even force quitting apps is not an option and in those situations, restarting the Mac is probably the only option left to you