Skip to content

No test for engine-internal rw_mutex thread safety #110

Description

@bibidhSubedi0

Description

ConcurrentAccessTest uses an external std::mutex to serialize access. This proves the server's external lock works, but doesn't test the engine's own rw_mutex. If the server-level lock is ever removed, data races go undetected.

Recommended Fix

Add a test that exercises the engine's internal locking by calling insert() and search() from different threads without the external mutex (using std::shared_mutex directly).

Metadata

Metadata

Assignees

No one assigned

    Labels

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions