System
Crash Reports
macOS and Linux save post-crash diagnostics as structured report files so developers and support tools can inspect what happened after an app, service, or kernel component failed. These folders accumulate .crash, .ips, and related DiagnosticReports on macOS, plus apport-style .crash dumps and metadata in /var/crash on Linux, often including stack traces, exception details, and launch context. Kudu removes these old crash report files to reclaim space without touching the apps themselves, your documents, accounts, or system settings.
Why clean Crash Reports?
- Repeated app or service failures can leave hundreds of retained .crash or apport dump files behind, and the symptom users notice is disk space steadily disappearing even after the crashing app is uninstalled
- Large crash dumps from browser, IDE, or VM processes can consume gigabytes in one incident, leading to low-storage warnings, failed updates, or apps refusing to save files until space is freed
- On Linux, stale apport crash files can keep a previously reported failure looking unresolved, so users continue seeing crash notifications or report prompts for problems that no longer occur
- macOS DiagnosticReports folders often preserve years of historical reports, making it harder to find the current failure because Console and support workflows are cluttered with old incidents
- When a crash loop fills the report directory with near-identical dumps, the visible symptom is repeated report generation and a rapidly growing Logs or /var partition that slows other maintenance tasks
- Old reports can capture executable paths, loaded modules, and recent process state that are no longer relevant, so clearing them reduces leftover diagnostic clutter without deleting any actual app data or preferences
What gets cleaned
Cache paths Kudu targets
macOS
~/Library/Logs/DiagnosticReports |
Linux
/var/crash |
Frequently asked
Common questions about Crash Reports
Related cleaners
Free & open source
Download Kudu and reclaim your disk space.
Available on Windows, macOS, and Linux. No account required, no feature gates, no telemetry without consent. All cleaning targets are open source and community-auditable.