Add Crashpad offline native crash replay support #193
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
- Start a CrashReportUploadThread during Crashpad initialization. - Enable watch_pending_reports so pending native crashes from previous runs are retried automatically. - Store Backtrace URL and pass it to the upload thread. - Update DisableCrashpad()/ReEnableCrashpad() to stop/start the thread.
rick-bt
approved these changes
Nov 17, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Context
Crashpadwrites native crashes to its database when offline but does not automatically retry them on Android.This PR adds
CrashReportUploadThreadthat runs at startup and uploads any pending reports.Changes
Native crashes that occur offline are now correctly uploaded when the app restarts with network connectivity.
Sample Reports
implements: backtrace-labs/crashpad#75
ref: BT-6268