LockDown Browser High CPU Usage on Mac (Diagnostics + Fix Guide)

Last updated 2026-05-02 · LDBypass Editorial

Baseline expectations (per our benchmark)

If your actual sustained CPU is >1.5× the expected upper bound, troubleshoot.

Diagnostic ladder

Step 1: Verify LDB is native arm64 (not Rosetta)

Activity Monitor → search "LockDown Browser" → check "Kind" column.

• "Apple": native arm64. Expected baseline applies.
• "Intel" on Apple Silicon: running through Rosetta 2. Expect ~30-50% higher CPU.

If "Intel": reinstall fresh from your LMS (see Rosetta page).

Step 2: Pause real-time antivirus

Most common cause of elevated CPU. Malwarebytes, Bitdefender, Sophos, Norton scan every Monitor video buffer write, doubling effective CPU cost.

Workaround: pause AV for the exam window. See AV conflicts page.

Step 3: Disable Spotlight indexing during exam

sudo mdutil -i off /

Disables Spotlight indexing system-wide. Re-enable after exam:

sudo mdutil -i on /

Reclaims 5-10% CPU if Spotlight was actively indexing.

Step 4: Quit cloud sync (Dropbox, OneDrive, Google Drive)

See cloud sync conflicts page.

Step 5: Disconnect external monitors

Mirroring or extending to a second display adds CompositingServer overhead. Disconnect for the exam.

Step 6: Enable Low Power Mode

System Settings → Battery → Low Power Mode → On while on battery. Caps CPU clock; can reduce LDB CPU by ~20% on the Air-class chips.

If CPU is high even after all of the above

Less common causes:

• Hardware accelerated WebKit disabled in some accessibility configurations. System Settings → Accessibility → toggle Reduce Motion off if currently on.
• Stuck kernel extension from old AV/VPN. Reboot.
• Beta macOS build. Beta macOS routinely has performance regressions; downgrade to public release.

What's "normal" for the init spike

The first 3-5 seconds of LDB launch see CPU spike to 30-80% (during process scan + webcam initialization). This is expected and not a problem. Steady-state CPU after the exam UI loads is what matters.