LockDown Browser Unresponsive During Exam on Mac - Emergency Recovery

Last updated 2026-05-01 · LDBypass Editorial

Don't panic - what's actually at risk

The fundamental fact: your LMS, not LDB, holds your exam answers. LDB is a kiosk wrapper around your LMS's exam interface. Every answer you've clicked through is stored on Canvas/Blackboard/D2L Brightspace/Moodle servers, not in LDB's process memory.

What survives a freeze + force-quit:

• Every answer you saved by clicking Next or Previous.
• Every multiple-choice answer you clicked (most LMSes auto-save on click).
• The Monitor recording up to the freeze (Respondus uploads in chunks throughout the exam).
• The exam timer state (the LMS knows how much time is remaining).

What may not survive:

• The answer to the question you were currently typing in if the LMS doesn't auto-save mid-question (LMS-dependent - Canvas yes, Blackboard Original no).
• The unsaved portion of an essay if you'd been typing for > 30 seconds without clicking Next.

Escalation ladder during the freeze

1. Wait 30 seconds. Some freezes self-resolve as a slow operation completes. Don't force-quit immediately if the spinner is moving.
2. Try ⌘+Q. LDB blocks this in kiosk mode but occasionally accepts it during specific freeze states. If it works, the exam exits cleanly via the Submit dialog.
3. Force-quit. ⌘+⌥+Esc → LockDown Browser → Force Quit. See force-quit entity for details.
4. If force-quit dialog doesn't open, use Activity Monitor or last-resort terminal kill (also covered in the force-quit entity).
5. Open Safari, sign in to LMS, navigate to the exam. Most LMSes show "Resume Quiz" with elapsed time preserved.
6. If LMS shows "Auto-submitted" or "No in-progress attempt", email your instructor immediately. Provide:
   • Your name and the course number.
   • The exact time the freeze started.
   • Approximately how many questions you answered before the freeze.
   • Your macOS version and LDB version.
   • A screenshot of any error message.
7. If your university has an Academic Integrity office, copy them on the email. Documenting the failure proactively protects you from later misinterpretation.

What NOT to do

• Don't reboot before saving the diagnostic report. ~/Library/Logs/DiagnosticReports/LockDown Browser-*.ips contains the crash signature your instructor / IT can use to verify the freeze.
• Don't repeatedly relaunch LDB on the same exam without your instructor's explicit go-ahead. Multiple Monitor recording sessions on the same exam log as suspicious.
• Don't open browser tabs to research the question while LDB is force-quit and the LMS exam is "paused". The Monitor recording captures up to the freeze, but your instructor reviewing the timeline will see what you did between the freeze and the email.
• Don't try to bypass LDB by accessing the LMS exam directly in Safari while LDB is supposed to be running - most LMSes detect non-LDB access during a LDB-required exam and flag it.

How to prevent this from happening on the next exam

1. Run the practice exam your instructor enabled, on the same Mac, the day before. Catches TCC failures and blacklist conflicts in advance.
2. Update macOS and LDB to the latest versions in the days before the exam (not the morning of).
3. Quit every other application before launching LDB.
4. Disconnect external monitors, AirPods (use built-in mic for system check), and external webcams that you don't need.
5. Charge to 100% and plan to take the exam plugged in if it's > 90 minutes.
6. Disable any third-party antivirus's real-time scanning for the exam window.

If the freeze leads to academic-integrity escalation

Most universities have policy frameworks for technical failures during proctored exams. Common provisions:

• The student notifies the instructor within 24 hours.
• The instructor consults the LMS log + the Monitor recording.
• If the failure is corroborated, the student is offered a re-take or a grade based on completed-questions only.
• If the recording shows extended unexplained behaviour between freeze and recovery, the integrity question is opened.

The single most important thing: email immediately. The 24-hour notification window is non-negotiable at most institutions. Your saved .ips crash report is your strongest evidence.