Make all update_client ref counted types RefCountedThreadSafe.
Per-project coding style: ref counted types must be thread-safe and sequence affinity declared with sequence checkers in destructors if needed. The motivation for such change is that our types get aggregated in different ways, and mixing thread-safe and non thread-safe may result into puzzling asserts in ref-counting code when objects get shared between sequences. Bug: 1105922 Change-Id: Ie3b182b31765d0416ae5d6ca108782843b95528e Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2314677Reviewed-by:Joshua Pawlicki <waffles@chromium.org> Commit-Queue: Sorin Jianu <sorin@chromium.org> Cr-Commit-Position: refs/heads/master@{#791248}
Showing
Please register or sign in to comment