fast-wait-free-queue icon indicating copy to clipboard operation
fast-wait-free-queue copied to clipboard

Avoid double-free by only freeing each queue once

Open KvGeijer opened this issue 1 year ago • 0 comments

This was mainly an issue with LCRQ, which actually implements a free function. However, this function was called from every thread when they exited, leading to a segmentation fault in most runs. Now it only lets a single thread free the queue in the benchmarks.

KvGeijer avatar Sep 11 '24 20:09 KvGeijer