Skip to content

Potential deadlock in TSAN #57367

@tavplubix

Description

@tavplubix

https://s3.amazonaws.com/clickhouse-test-reports/57339/84abbafcc5895d21fde4417b541a43c33cd00dcf/stress_test__tsan_.html

Postprocessed stacktraces: https://pastila.nl/?00024630/32cdf0ea32e817c70b431e043add8616#NWtYs/CbuaYiH4jpqiAsvw==

Most threads are waiting in 0x00005603e04a533a in __sanitizer::FutexWait(__sanitizer::atomic_uint32_t*, unsigned int) () and 0x00005603e04a58e5 in __sanitizer::StaticSpinMutex::LockSlow() ()

Threads that are not inside TSAN: https://pastila.nl/?00082fa0/0e902cfeef9c056aa77694d2f135620b#o6bf3vFc/T4GXN74kUnojw==

It could be a bug in TSAN, needs further investigation

Metadata

Metadata

Assignees

No one assigned

    Labels

    fuzzProblem found by one of the fuzzers

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions