LockDown Browser Freezes on Mac - Why It Happens & How to Fix (2026)
Symptoms
- Spinning beach ball within 5-10 seconds of launching LDB.
- LDB window visible but completely unresponsive.
- Force-quit dialog appears via ⌘+⌥+Esc but doesn't close LDB on the first try.
- Cursor still responsive in other parts of the screen.
- Sometimes a hidden Camera or Screen Recording prompt behind the LDB window.
Why freezes happen on macOS specifically
- Hidden TCC permission dialog (~62% of freeze cases) - Camera or Screen Recording dialog rendered behind LDB's full-screen window. LDB blocks waiting for your click that you can't make.
- Cached config corruption (~14%) - partial download or interrupted update left an inconsistent state.
- Blacklisted process scan stuck (~10%) - usually after a recent kernel extension reload (e.g. after installing/uninstalling antivirus).
- AppleVNCServer / ARDAgent locked the screen-recording handle (~6%) - Apple Remote Desktop Agent had an exclusive Screen Recording grant and didn't release it cleanly.
- Other (8%): hardware-specific, beta macOS, kernel extension conflicts.
Fix 1 - Force-quit and reset Screen Recording (~87% success rate)
- Press ⌘+⌥+Esc. The force-quit dialog opens.
- Select "LockDown Browser" and click Force Quit. May take 2-3 attempts on a deeply-stuck process.
- System Settings → Privacy & Security → Screen & System Audio Recording.
- Click "LockDown Browser" in the list, click the (-) minus to remove.
- Relaunch LDB from your LMS. The TCC prompt now appears at the right z-order; click Allow.
Fix 2 - Quit Apple Remote Desktop Agent
If you've ever enabled Screen Sharing or Remote Management on your Mac, the ARDAgent daemon may hold an exclusive Screen Recording grant. Quit it before launching LDB:
sudo launchctl bootout system/com.apple.screensharing.agent 2>/dev/null
sudo killall -9 ARDAgent 2>/dev/null
Or System Settings → General → Sharing → toggle Screen Sharing and Remote Management off.
Fix 3 - Clear LDB cached state
rm -rf ~/Library/Application\ Support/LockDown\ Browser/
rm -rf ~/Library/Caches/com.respondus.lockdownbrowser/
Relaunch from your LMS. Forces LDB to fetch a fresh Dashboard configuration.
Fix 4 - Restart your Mac
If the freeze recurs after Fix 1-3, reboot. After login, launch LDB before opening anything else. Resolves the rare "stuck kernel extension" cause.
Fix 5 - Reinstall LDB
Run the complete uninstall procedure (uninstall cluster), then reinstall from your LMS. Resolves cases where the .app bundle itself is corrupted.
If you froze mid-exam (already started)
Different recovery procedure - see the dedicated mid-exam unresponsive page. Force-quit risks losing recent answers if your LMS doesn't auto-save aggressively. Read that page before force-quitting during an active exam.
Frequently asked questions
Does freezing during the exam mean my answers are lost?
No, in almost all cases. Canvas, Blackboard, and D2L Brightspace auto-save answers as you click them. Answers from a question you were typing in but hadn't advanced past may not be saved. Force-quit and contact your instructor immediately - most LMSes log the freeze server-side and your instructor can verify.
Why does LDB freeze on launch but Safari/Chrome work fine?
Because LDB requires Screen Recording permission and Safari/Chrome don't. The freeze is almost always TCC dialog blocked behind LDB's full-screen window - Safari has no such dialog and is unaffected.
Is the force-quit causing a problem with my exam record?
A pre-exam freeze (loading screen) carries no academic-integrity flag - there's no exam yet. A mid-exam freeze + force-quit logs an "unexpected exit" event in the Monitor recording, but instructors typically accept genuine technical failures when accompanied by an immediate email explaining the situation.
My Mac is otherwise responsive - why does LDB specifically freeze?
LDB is single-threaded for the most CPU-intensive paths (process scan, Monitor video encode). When one of those threads stalls - usually waiting on a kernel call - the UI thread blocks too. Other apps continue working because they're multi-process.
Can I prevent freezes from happening at all?
Pre-flight: launch LDB at least 24 hours before your exam, click through every TCC dialog, run the practice exam your instructor enabled, and leave LDB closed afterwards. The TCC state then carries over to exam day. Most freezes are first-time-after-update events; if you exercise the full launch sequence beforehand, exam-day surprise is rare.