LockDown Browser + Dropbox / OneDrive / Google Drive Conflict on Mac
The symptom
LDB launch freezes for 5-15 seconds (sometimes 60+ seconds on Macs with very large Dropbox libraries). Webcam check delayed. Periodic stutter during the exam as cloud sync polls the cache directory.
Why it conflicts with LDB
Each cloud sync product installs a FinderLoadBundle handler that hooks into macOS's file system event stream. They watch the entire user home directory for changes. When LDB writes to ~/Library/Application Support/LockDown Browser/ during launch, all three handlers fire simultaneously, each scanning the new files for selective-sync rules.
The fix - pre-exam procedure
- Dropbox: Status menu icon → Settings (gear) → Quit Dropbox. Verify no
Dropboxprocesses remain in Activity Monitor. - OneDrive: Status menu icon → Settings → Quit OneDrive. Verify no
OneDriveprocesses. - Google Drive Desktop: Status menu icon → Quit Google Drive. Verify no
Google Driveprocesses. - Box Drive (corporate users): Same - quit entirely.
- iCloud Drive: Cannot be quit (system service). Does NOT exhibit the same delay because Apple's CloudDocs daemon is more conservative about scanning. Leave iCloud Drive alone.
Alternative configurations
If you want to avoid quitting/restarting cloud sync regularly:
- Pause sync (most clients have a "Pause sync for 1 hour" option in their menu) instead of quitting.
- Add
~/Library/Application Support/LockDown Browserto selective-sync exclusions. Won't fully eliminate the delay but reduces the file-event volume. - Take exams from a laptop without cloud sync installed (less practical).
What NOT to do
- Don't try to bypass the conflict mid-exam - LDB's blacklist scan happens before exam launch and re-runs at intervals.
- Don't restart the conflicting app DURING the exam - LDB will detect the new process and may flag.
- Don't leave the conflicting app paused/disabled long-term outside exam windows; that's overkill for non-LDB use.
Frequently asked questions
Will my files lose sync progress if I quit Dropbox mid-upload?
No - Dropbox resumes from the last checkpoint when relaunched. Quit and resume is safe.
iCloud Drive doesn't cause issues. Why?
Apple's implementation is more conservative - it doesn't scan ~/Library/Application Support/ in real-time. Third-party cloud sync (Dropbox, OneDrive, Google Drive) is more aggressive about file-system event monitoring.
What about Backblaze, Carbonite, or other backup clients?
Same pattern - pause or quit before exam. Especially Backblaze, which scans aggressively.