** (WebKitWebProcess:1964): ERROR **: 17:03:28.556: WebProcess didn't exit as expected after the UI
** (WebKitWebProcess:1964): ERROR **: 17:03:28.556: WebProcess didn't exit as expected after the UI process connection was closed
Immediate Remediation
bash
# Disable the WebKit web process sandbox (debugging only) WEBKIT_DISABLE_SANDBOX_THIS_IS_DANGEROUS=1 your-app # If that doesn't help, also disable GPU compositing WEBKIT_DISABLE_COMPOSITING_MODE=1 your-app
Root Cause Analysis
The WebProcess (a separate rendering process) terminated unexpectedly after the UI process closed its connection—typically caused by a sandbox restriction, GPU/driver crash, or resource exhaustion (e.g., file descriptor limits, OOM).
Verification & Guardrails
- Disabling the sandbox removes a critical security boundary; only use temporarily to confirm the cause.
- Check `dmesg` or `journalctl -xe` for the actual crash signal (e.g., `segfault`, `SIGKILL`), and update `webkit2gtk` to the latest version.
Have a custom or uncategorized crash?
Run your trace through our in-memory client privacy sandbox for instant SRE remediation.