Avidemux vs Crashpad
Avidemux
avidemux.sourceforge.netCrashpad
chromium.googlesource.comSide by side
| Figure | Avidemux | Crashpad |
|---|---|---|
| Price from | Free | Free |
| Free plan | Yes | Yes |
| Free trial | — | — |
| Open source | Yes | — |
| Web | Yes | — |
| Windows | Yes | Yes |
| macOS | Yes | Yes |
| Linux | Yes | Yes |
| iOS | — | Yes |
| Android | — | Yes |
| Plans published | 2 | 1 |
| Spec score · Game Crash Reporting Software | 8.2 (#13) | 8.7 (#10) |
| Purpose | Avidemux is a free video editor designed for simple cutting, filtering and encoding tasks. | Crashpad is a library for capturing, storing, and transmitting postmortem crash reports from an application to a collection server. |
Plans
In their own words
Avidemux
Avidemux has no write-up on Specifiction yet; its figures are above.
Crashpad
Crashpad is an open-source crash-reporting system and client library for Android, iOS, Linux, macOS, and Windows. It embeds in an application, where a handler snapshots a registered process after a crash, saves a dump, and can send it to a collection server configured by the embedding client. Applications can also request process-state dumps on demand for diagnostics. Reports use the Windows minidump format with Crashpad extensions and generally contain loaded modules, thread registers and stack memory, selected operating-system state, and memory referenced by registers and stacks. Applications can add key/value annotations, application-specific metadata, and custom minidump streams. Uploads use HTTP or HTTPS through the Breakpad wire protocol, with a documented limit of one upload per hour and failed uploads aborted. The design requires applications to obtain and honor consent because process memory may contain sensitive data. Crashpad is a client-side component; a processor is planned without a completion timeline.