---
title: "ReportCrash and SubmitDiagInfo on Mac: crash reports and analytics · Kilobat Guides"
url: "https://kilobat.app/guides/what-is-reportcrash.html"
description: "ReportCrash saves crash reports and SubmitDiagInfo sends diagnostic data to Apple when you opt in. See their traffic and the Analytics setting."
---

macOS processes

# What are ReportCrash and SubmitDiagInfo on Mac?

`ReportCrash` saves crash reports on the Mac. `SubmitDiagInfo` sends diagnostic information to Apple, but only if you opted in.

Process: `SubmitDiagInfo` · Process: `ReportCrash` · Applies to: macOS 13 Ventura and later for the System Settings path. Seen on macOS 27.2. · Checked: 29 October 2026

## Where you see it

- `SubmitDiagInfo` is in the list in Activity Monitor › Network, in `nettop` or in Kilobat.
- A firewall or network monitor asks if `SubmitDiagInfo` can connect.
- A short upload appears with no app open.

## What it is

The ReportCrash man page says that it analyzes crashing processes and saves a crash report to disk. launchd starts it when a crash occurs.

The SubmitDiagInfo man page says that it runs periodically. If you opted in, it sends recent diagnostic information to Apple.

## Why it uses the network

- **Diagnostic uploads.** With Share Mac Analytics on, SubmitDiagInfo sends crash, hang and usage information to Apple.
- **Reports that you send.** When you click Report after a crash, the report goes to Apple.

## Is it normal?

Yes, if you share analytics. The uploads are small and periodic.

ReportCrash itself writes to disk. Its man page does not describe network use.

## See how much it uses

1. Open Activity Monitor from Applications > Utilities. Click Network.
2. Type `SubmitDiagInfo` in the search field. The Sent Bytes and Rcvd Bytes columns show what it moved.
3. In Terminal, watch only this process. Press d to show the change per second, and q to quit.

   ```
   nettop -p SubmitDiagInfo -P
   ```

## Reduce or pause it safely

1. Choose Apple menu > System Settings > Privacy & Security. Click Analytics & Improvements.
2. Turn off Share Mac Analytics. Turn off Share with app developers too, if you want.
3. Keep crash reporting itself on. Developers use the reports on your Mac to fix problems.

## With Kilobat

1. Open the Kilobat app list and search for `SubmitDiagInfo`. Its row shows the live rate and the bytes it moved.
2. In Terminal, see the same live list. Press / and type the name to search.

   ```
   kilobat status --watch
   ```
3. Show its traffic over one day. Names match `kilobat report --summary`.

   ```
   kilobat bandwidth SubmitDiagInfo day
   ```
4. Through MCP, an AI agent gets the same history with `get_app_bandwidth` and the name `SubmitDiagInfo`.
5. The live view is free. History in the app needs Pro. Kilobat records history only while the app runs.

## Questions

**Where are crash reports on my Mac?**

The ReportCrash man page says that reports for apps are in `~/Library/Logs/DiagnosticReports`.

**Does SubmitDiagInfo send data if I said no?**

The man page says that it sends nothing unless you opted in.

## Sources

- ReportCrash(8) and SubmitDiagInfo(8), man page installed with macOS 27.2
- [Apple Support: Share analytics information from your Mac with Apple](https://support.apple.com/guide/mac-help/share-analytics-information-mac-mh27990/mac)
- nettop(1), man page installed with macOS 27.2

Sources checked on 29 October 2026. Man pages are the ones installed with macOS; open one with `man <name>` in Terminal.

## Related guides

- [What is symptomsd on Mac?](https://kilobat.app/guides/what-is-symptomsd.html): symptomsd provides services for Apple's Symptom Framework.
- [Find which app uses your bandwidth on a Mac](https://kilobat.app/guides/which-app-uses-bandwidth.html): Activity Monitor and nettop show which processes send and receive data.