core: deadlock in chainmanager after posting RemovedTransactionEvent#1865
Merged
obscuren merged 1 commit intoethereum:developfrom Oct 2, 2015
Merged
Conversation
This PR solves an issue with the chain manager posting a `RemovedTransactionEvent`, the tx pool will try to acquire the chainmanager lock which has previously been locked prior to posting `RemovedTransactionEvent`. This results in a deadlock in the core.
Updated: Fri Oct 2 10:23:58 UTC 2015 |
Contributor
|
👍 |
obscuren
added a commit
that referenced
this pull request
Oct 2, 2015
core: deadlock in chainmanager after posting RemovedTransactionEvent
sduchesneau
pushed a commit
to streamingfast/go-ethereum
that referenced
this pull request
Nov 20, 2025
* consensus, internal: don't limit gas cap for system txns * internal/ethapi: handle nil receiver
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
3 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.
This PR solves an issue with the chain manager posting a
RemovedTransactionEvent, the tx pool will try toacquire the chainmanager lock which has previously been locked prior to
posting
RemovedTransactionEvent. This results in a deadlock in thecore.