Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

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? Sign in to your account

Jump to bottom

Fix for data race in StorageMerge #6717

Merged
merged 1 commit into from
Aug 29, 2019
Merged

Fix for data race in StorageMerge #6717

merged 1 commit into from
Aug 29, 2019

Conversation

alexey-milovidov
Copy link
Member

For changelog. Remove if this is non-significant change.

Category (leave one):

  • Bug Fix

@alexey-milovidov
Copy link
Member Author

FATAL: ThreadSanitizer CHECK failed: /build/llvm-toolchain-8-8.0.1~svn363027/projects/compiler-rt/lib/sanitizer_common/sanitizer_deadlock_detector.h:69 "((n_all_locks_)) < (((sizeof(all_locks_with_contexts_)/sizeof((all_locks_with_contexts_)[0]))))" (0x40, 0x40)

@alexey-milovidov alexey-milovidov merged commit c19e5fa into master Aug 29, 2019
@KochetovNicolai KochetovNicolai added pr-bugfix Pull request with bugfix, not backported by default v19.12 labels Sep 19, 2019
KochetovNicolai pushed a commit that referenced this pull request Sep 19, 2019
@alexey-milovidov @KochetovNicolai
Merge pull request #6717 from yandex/fix-data-race-in-storage-merge
1b63687 
Fix for data race in StorageMerge

(cherry picked from commit c19e5fa)
KochetovNicolai pushed a commit that referenced this pull request Sep 20, 2019
@alexey-milovidov @KochetovNicolai
Merge pull request #6717 from yandex/fix-data-race-in-storage-merge
4aa46c6 
Fix for data race in StorageMerge

(cherry picked from commit c19e5fa)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers
No reviews
Assignees
No one assigned
Labels
pr-bugfix Pull request with bugfix, not backported by default
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
2 participants
@alexey-milovidov @KochetovNicolai