8495449f07
TSAN identified a data race between updates to the states_ map (ex. in Mock::UnregisterLocked) and the iteration done in this destructor. Writes to the map use g_gmock_mutex, but the destructor does not acquire it. Acquiring the lock here fixes the data race. It should only be possible to trigger this TSAN finding in cases where a mock object is deleted by a thread other than the main thread. PiperOrigin-RevId: 591935393 Change-Id: I9dd1faa40058d78e165a91333346514b4b73365c |
||
|---|---|---|
| .. | ||
| gmock_main.cc | ||
| gmock-all.cc | ||
| gmock-cardinalities.cc | ||
| gmock-internal-utils.cc | ||
| gmock-matchers.cc | ||
| gmock-spec-builders.cc | ||
| gmock.cc | ||