accounts/scwallet: remove selfDerive start from Initialize to avoid goroutine leak #32897
+0
−1
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Remove the go w.selfDerive() invocation from Wallet.Initialize. Starting the self-derivation loop here launches a goroutine before w.deriveReq and w.deriveQuit are initialized, causing the loop to block forever on a select over nil channels. Later, Open correctly initializes the channels and starts another selfDerive, leaving the first goroutine stuck and unkillable. The self-derivation lifecycle should begin in Open only, after channels are set up. This change aligns with the USB wallet backend pattern and prevents leaked goroutines.