Native crash capture on Windows and Linux
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 28/100
- Issue type
- Feature
- Clarity
- Needs clarification
- Activity status
- Active
- Domain
- desktop, observability-sre, testing-qa
Research direction
Start by reviewing PR #621 and the existing Dart exception-capture path, then define the Windows/Linux native integration points and consent behavior. Add the native integration tests described here using a crashing test plugin or FFI library, and verify next-launch reporting, opt-out behavior, matching symbol artifacts, and documented limitations.
Written by the indexing model from the issue text.
Description
Problem Statement
PR #621 adds Windows/Linux support but explicitly excludes native crash capture. Dart error hooks cannot reliably observe crashes in the Flutter engine, native plugins, or libraries called through dart:ffi when those failures terminate the process before Dart callbacks execute.
Examples include Windows access violations and Linux segmentation faults or aborts. These failures currently have no desktop native crash-reporting path in the SDK. This is a follow-up feature request, not a blocker for the documented scope of #621.
Solution Brainstorm
Add opt-in native crash capture for Flutter applications on Windows and Linux:
- Integrate platform-appropriate crash collection for supported native engine/plugin/FFI failures.
- Persist crash records safely and report them on the next launch when immediate delivery is impossible, respecting consent and SDK configuration.
- Include native stack addresses, matching loaded-image/debug identifiers, and app/build context. Document the required symbol-upload workflow and supported symbol formats for readable stacks.
- Document limitations clearly; do not promise capture of every process termination, hang, or out-of-memory failure.
Validation
Add native Windows/Linux integration tests that deliberately trigger a crash in a test plugin or FFI library, restart the application, and verify the resulting $exception event. Cover opt-out behavior and release-build symbolication with matching artifacts.
Keep this distinct from Dart exception capture, background-isolate forwarding, and Dart obfuscated-stack support.
Related
- Desktop support: #51
- Initial Windows/Linux implementation: #621
- Android-native crash tracking: #490 (different platform scope)
- Dominant language
- Dart
- Stars
- 99
- Forks
- 94
- Avg merge
- 2d 4h
- Merged PRs (30d)
- 65
Getting set up
- No Dockerfile or Docker Compose file
- Has a pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from PostHog/posthog-flutter
-
Android bug
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
PostHog/posthog-flutter#731 · 1 comment ·
Maintainers usually reply within 1 day
-
dependencies enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
PostHog/posthog-flutter#377 · 3 comments ·
Maintainers usually reply within 1 day
-
Support widgetOpenenhancement
Difficulty 4/5 3-5 days Newbie friendliness 30/100
PostHog/posthog-flutter#596 · 1 comment ·
Maintainers usually reply within 1 day
-
enhancement feature/replay
Difficulty 4/5 3-5 days Newbie friendliness 52/100
PostHog/posthog-flutter#593 · 5 comments ·
Maintainers usually reply within 1 day
-
Session replay: support v2 trigger groups (conditional recording)Possibly taken @marc-merino claimed this 39 days ago. Openenhancement feature/replay
Difficulty 5/5 Over a week Newbie friendliness 35/100
PostHog/posthog-flutter#545 ·
Maintainers usually reply within 1 day
All issues in PostHog/posthog-flutter
Similar issues
-
bug enhancement needs-triage
Difficulty 2/5 1-3 hours Newbie friendliness 62/100
-
bug from-telegram platform:windows
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
hiddify/hiddify-app#2592 ·
Maintainers usually reply within 1 day
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 62/100
cogwheel0/conduit#1122 · 1 comment ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
bannzai/shoppinglist#779 ·
Maintainers usually reply within 1 day
-
[BUG] JEFIT import fails because # characters are not recognisedPossibly taken A pull request linked to this issue is open or already merged. Openbug
Difficulty 1/5 Under an hour Newbie friendliness 88/100
Maintainers usually reply within 1 day