oh-arkruntime-thread-safety-audit

To find thread-safety races in ArkTS-Sta, audit ETS code for risky shared static state like global singletons and caches, then verify reachability through concurrent entry points like taskpool and EAWorker.

Audit concurrency reachability by scanning ETS stdlib and plugin code for static candidates, then checking if taskpool, EAWorker, or callback paths can reach that shared state to classify race risks.

The best way to fix data races is applying synchronization strategies like atomics, concurrent containers, or mutex lock-guarded invariants, followed by running targeted TSAN-aligned concurrent tests for validation.

This thread-safety audit targets ETS code in static_core/plugins/ets, including stdlib and tests, applying native follow-up only when needed after completing the multi-phase ETS scanning and risk classification.

You need atomic synchronization or mutex invariants when shared mutable static state in ETS code is reachable via concurrent paths, requiring risk classification before proposing changes and validation tests.

Shared mutable static state causes data races under ArkTS-Sta concurrency when global registries or singletons are accessed simultaneously through taskpool or EAWorker paths without atomic or mutex synchronization.