fix: Recover from a crash more gracefully#3440
Merged
FrederikBolding merged 3 commits intomainfrom Jun 5, 2025
Merged
Conversation
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## main #3440 +/- ##
=======================================
Coverage 98.16% 98.16%
=======================================
Files 402 402
Lines 11123 11128 +5
Branches 1759 1760 +1
=======================================
+ Hits 10919 10924 +5
Misses 204 204 ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
GuillaumeRx
approved these changes
Jun 5, 2025
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
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.
The current behavior for stopping Snaps (in case of crashes or idling) was prone to race conditions when requests to the Snap were dispatched around the time that the Snap crashed.
We saw this in production here: MetaMask/metamask-extension#33411
To prevent this, we can turn the
stoppingflag into a promise that we can await in case of multiple calls tostopSnap, but also before considering whether the Snap is started for a subsequent request.