We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and
privacy statement. We’ll occasionally send you account related emails.
Already on GitHub?
to your account
Submitted by: @dyemanov
Is related to CORE3521
Can be easily reproduced with SuperClassic. Other architectures are either not affected or harder to reproduce.
Introduced with CORE3521, so the only affected official version is v2.5.1.
It looks like a bad idea to acquire the backup state lock after it has been destroyed.
Commits: ec6c21f 7d22e58
The text was updated successfully, but these errors were encountered:
Link: This issue is related to CORE3521 [ CORE3521 ]
Sorry, something went wrong.
assignee: Vlad Khorsun [ hvlad ]
Fix Version: 2.5.2 [ 10450 ]
Fix Version: 3.0 Alpha 1 [ 10331 ]
status: Open [ 1 ] => Resolved [ 5 ]
resolution: Fixed [ 1 ]
status: Resolved [ 5 ] => Closed [ 6 ]
status: Closed [ 6 ] => Closed [ 6 ]
QA Status: No test
No branches or pull requests