Skip to content

Thread safety issue if two clfftBakePlan() calls, on different objects, execute concurrently #240

@azonenberg

Description

@azonenberg

Using latest clfft binary packages for Debian, I get an assertion failure:

glscopeclient: /build/clfft-8xRwfG/clfft-2.12.2/src/library/repo.cpp:217:
clfftStatus FFTRepo::setclProgram(clfftGenerators, const FFTKernelSignatureHeader*, _cl_program* const&,
_cl_device_id* const&, _cl_context* const&): Assertion `NULL == p' failed.

Adding mutexes to serialize the bake operations eliminates the assertion. I have to date not seen any issues with concurrent execution of FFTs issued from different threads, only the bake operation.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions