How do I safely force quit a frozen app on my Mac?

General
1

My Mac keeps freezing whenever I open one specific app, and I’ve had to hold the power button to shut the whole computer down. I’m worried that might damage files or the system. Can someone walk me through the safest way to force quit a stuck or unresponsive app on macOS, and any steps to avoid this happening again?

2

First, yes, holding the power button can corrupt files if it happens a lot, so using Force Quit is safer.

Try these in this order:

  1. Standard Force Quit

    1. Press Command + Option + Esc.
    2. A “Force Quit Applications” window appears.
    3. Select the frozen app.
    4. Click “Force Quit”.
    5. Confirm.

  2. From the Dock

    1. Right click the app icon in the Dock.
    2. Hold Option.
    3. “Quit” changes to “Force Quit”.
    4. Click that.

  3. From the Apple menu

    1. Click the Apple logo in the top left.
    2. Click “Force Quit”.
    3. Pick the app.
    4. Hit “Force Quit”.

If that fails and the whole system locks:

  1. Try a “soft” keyboard restart
    1. Press Control + Command + Power.
    2. This forces a restart faster than normal, but still safer than holding power for 10 seconds.

If nothing responds:

  1. Last resort hard power off
    1. Hold the power button until the screen goes dark.
    2. Wait 10–15 seconds.
    3. Power back on.
    4. After reboot, open Disk Utility.
    5. Run First Aid on your startup disk to check for file system issues.

To reduce future freezes with that one app:

  1. Update the app to the newest version.
  2. Update macOS.
  3. Try deleting the app and reinstalling it from the official source.
  4. Test in a new user account to see if it is a profile issue.
  5. Check Activity Monitor:
    1. Open Spotlight with Command + Space.
    2. Type “Activity Monitor” and hit Enter.
    3. Look for the app using huge CPU or memory.
    4. If stuck, select it and click the X in the toolbar, then “Force Quit”.

If the same app locks things every time, it is either buggy, incompatible with your macOS version, or has corrupted settings.

Quick preferences reset approach for one app:

  1. Quit the app.
  2. Go to ~/Library/Preferences.
  3. Find files named like com.developer.appname.plist.
  4. Move them to the desktop.
  5. Reopen the app and see if it behaves.
  6. If it works, delete the old plist files. If not, move them back.

Do frequent Time Machine backups so if the system gets damaged from repeated hard shutdowns, you still have your stuff.

Shortest version:
Use Command + Option + Esc first every time, only hold the power button when nothing responds at all. Run Disk Utility First Aid after any forced shutdown.

3

Couple of extra tricks that sit around what @jeff already covered, without rehashing the same steps:

1. Try “force quitting” from Terminal instead of the power button

When the UI is mostly dead but the system isn’t totally gone, Terminal can still work.

  1. Open Spotlight with Command + Space.
  2. Type Terminal and hit Enter.
  3. In Terminal, type:
    ps aux | grep -i appname
    Replace appname with a unique part of the app’s name.
  4. Find the line for that app, note the PID number (first big number after your username).
  5. Then:
    kill PID
    If it ignores that:
    kill -9 PID

This is basically the nuclear option for that one app, instead of nuking your whole Mac with the power button.

2. Use Activity Monitor more intentionally

Jeff mentioned Activity Monitor, but I’d go one step further: keep it open while you test that app.

  1. Open Activity Monitor.
  2. Sort by CPU or Memory.
  3. Start the problematic app and watch:
    • If it spikes CPU to 300% and stays there, that’s a runaway process.
    • If memory usage climbs like a rocket until you hit “Memory Pressure” in red, that can hang the whole machine.

That tells you if the issue is:

  • The app itself going nuts
  • Or the app pushing your whole system over the edge

If it’s killing the whole system, sometimes quitting other heavy apps in Activity Monitor first gives you enough breathing room to then quit the bad one.

3. Disable auto reopen to avoid instant re-freeze

Super important if your Mac keeps relaunching that app when you log in.

  1. When you restart after a crash, on the login screen:
    • Uncheck “Reopen windows when logging back in.”
  2. Once logged in, go to:
    • System Settings → General → Login Items
    • Remove that app from the list if it’s there.

Otherwise you restart, macOS proudly reopens your “last session,” and boom, freeze again. Ask me how I found that out the hard way…

4. Boot into Safe Mode to deal with the app

If the app freezes the system every single time:

  1. Shut down the Mac.
  2. Turn it on and immediately:
    • Intel: Hold Shift until you see the login window.
    • Apple Silicon: Hold power until you see “Options,” select your disk, then hold Shift and click “Continue in Safe Mode.”
  3. Log in.
  4. In Safe Mode, uninstall the app, or:
    • Move it out of Applications temporarily
    • Remove related login items or helper tools

Safe Mode runs fewer background processes and extensions, which can keep the freeze from happening long enough for you to clean house.

5. Avoid overusing the “soft restart” keys

Slight disagreement with @jeff here: Control + Command + Power is better than holding the button forever, but it can still interrupt writes and cause corruption if you lean on it a lot.

My personal order of operations:

  1. Try Force Quit / Activity Monitor / Terminal kill.
  2. Try logging out with Command + Shift + Q if you can still reach the menu.
  3. Only then go to Control + Command + Power.
  4. Absolute last: hold power.

And after any of the non‑clean shutdowns, yeah, running Disk Utility First Aid is smart.

6. Make the app less likely to kill everything

Besides prefs and reinstall:

  • Check for plugins / add‑ons in that app
    Some apps load third‑party extensions that are the real culprits. Disable them all, then re‑enable one at a time.

  • Try running it with a totally clean environment
    In Terminal:

    open -na '/Applications/AppName.app'

    The -n and -a flags can sometimes avoid stale state from previous runs.

  • Check crash logs
    Open Console → Crash Reports → look for that app.
    If you see repeated reference to a particular plugin, framework, or GPU call, that’s your suspect.

Short version:
Use every tool you can to kill just the misbehaving app (Terminal, Activity Monitor, Safe Mode cleanup) and treat holding the power button like pulling the plug on a desktop: only when the whole thing is stone dead, and expect to check the disk afterward.

4

Couple of angles that sit beside what @jeff and others have covered, focusing on preventing future freezes and file damage rather than just recovering from them.

1. First, verify the system is not the real culprit

Before you keep blaming that one app:

  • Check disk health

    • Open Disk Utility
    • Run First Aid on your system volume
      If there is disk-level corruption, any heavy app can trigger hangs. Repeated hard power-offs make this more likely, so fix this early.

  • Run Apple Diagnostics

    • Shut down
    • Turn on and hold D (Intel) or hold power and choose Diagnostics (Apple Silicon)
      A failing SSD, RAM issue, or GPU quirk can present as “this app freezes everything.”

If those flag anything, solve that before you chase the app.

2. Make macOS more resilient when an app goes rogue

You cannot fully stop an app from misbehaving, but you can reduce collateral damage:

  • Turn off “reopen windows” globally
    System Settings → Desktop & Dock → uncheck “Close windows when quitting an application” is often recommended, but for your case you want the opposite behavior:

    • On macOS versions that support it, disable automatic reopening of windows at login and app relaunch. That way, the system is not constantly restoring a broken state for that app.

  • Disable automatic document saving for that app (if it supports it)
    Some pro apps let you choose how often they autosave or whether they keep giant backup files open. Heavy autosave can lock the UI when the app goes sideways. Set a longer autosave interval or manual saves-only while troubleshooting.

  • Create a dedicated user account for that app

    • System Settings → Users & Groups → add a new user
      Run only that application there.
      Benefits:
    • Fresh prefs, caches, login items
    • If it hangs, at least your main session and open docs in your primary account are safe

You can switch users via the fast user switching menu instead of fully logging out.

3. Tweak how you force quit, not just whether you force quit

I disagree a bit with the idea that kill -9 is just a “nuclear but fine” option. It is effective, but it cuts the app off without letting it run any cleanup code.

General priority I recommend:

  1. Normal quit from Dock
    • Right click the icon → Quit
      This still works more often than it looks, especially if the UI is just sluggish, not frozen.
  2. Force quit via Dock
    • Right click icon → Option key → “Force Quit”
      This uses the system’s standard force quit behavior and is usually safer than jumping straight to kill -9.
  3. Force quit window
    • Command + Option + Escape
    • Select the app → Force Quit
  4. Only then resort to Terminal kill -9 if the app is zombie-level stuck.

If you have unsaved documents in other apps, sometimes waiting 1 to 2 minutes before doing anything drastic lets the system quietly finish writes in the background. It often feels frozen while Spotlight, Time Machine, or the disk controller is catching up.

4. Strip the app down to “bare metal”

Instead of just reinstalling:

  1. Reset the app’s preferences

    • Quit the app
    • In Finder, hold Option, click Go menu → Library
    • Look in Preferences and Application Support for folders or .plist files for that app
    • Move them to a temporary folder on the Desktop, do not delete yet
    • Relaunch the app
      If the hangs disappear, one of those config files was corrupt.

  2. Reset caches
    Same Library → Caches, find that app’s folder and move it out of the way.

  3. Test an older or newer version
    Sometimes only specific builds are buggy with your macOS version.

    • If you are on the latest version, try one version back.
    • If you are on an old build, upgrade.

Write down exactly which version of macOS and which version of the app you are using. Crashes often track to certain combos.

5. Don’t underestimate GPU and external display issues

If the freeze happens when you:

  • Open a specific window
  • Drag the app to a second monitor
  • Start playback or 3D / video preview

then the problem can be graphics related:

  • Temporarily disconnect external displays, docks, and hubs
  • Use only the built‑in screen and see if the hang persists
  • In apps that allow it, switch rendering from “Metal” or “OpenGL” to “Software” or “Compatibility” mode

GPU driver deadlocks can lock the entire UI and make it look like the app is the villain.

6. Backups: the unglamorous but important part

Forced shutdowns are most dangerous when you do not have current backups.

  • Set up Time Machine if you have not already
  • For critical files, consider a second backup target or a manual sync to cloud storage
  • After a few hard reboots, let Time Machine complete a full backup without interruption before more heavy testing

That way, if the worst case happens and the filesystem gets borked, you lose much less.

7. About the product title ’ and similar tools

Since you mentioned wanting safe ways rather than hardware panic:

Pros of using ’ in this context:

  • Can centralize troubleshooting documentation you keep about this whole freeze issue
  • Useful if it offers structured notes, task tracking, or guides that keep all your steps and observations organized
  • Helps you maintain a repeatable checklist of what you try when the Mac hangs, so you are not improvising under stress

Cons:

  • It does not itself fix kernel-level or filesystem problems
  • Extra software, if it is resident, can introduce its own background load
  • If it syncs or autosaves frequently, that is one more process doing writes while the system is already stressed

Used thoughtfully, ’ can improve your workflow around diagnosing the freezing app, but it is not a substitute for the built-in macOS tools and good backup hygiene.

@jeff already covered a lot of the core “how to kill the app instead of the whole Mac” stuff. I would just emphasize: mix that with preventive work like disk checks, separate user account tests, GPU isolation, and strict prioritization of clean quit methods. Over time you should reach a point where hard power holds are almost never necessary.