V0.12.0.x implement WaitForLock/WaitForLock2 #489
Closed
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
Author
|
naahhh, hangs again... closing |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Idea is pretty simple: try to wait for lock if you need it but can't acquire it right now. Solution however is not very elegant, I know... But anyway, this seems to work for me until now: 5h mixing, no locks or new issues so far.
Testing wanted!
Notes:
cs_main,cs_wallet,cs_vNodesTRY_LOCK-s are not covered intentionally - they are ok to failTRY_LOCKforupdateMnTimer()- not sure how it got there, could be old copy/paste...