Sequentialise access to callbacks in DWriteFontLookupTableBuilder
Since there may be multiple instance of DWriteFontProxyImpl instantiated for multiple RenderProcessHosts, and DWriteFontProxyImpl::GetUniqueNameLookupTable may access DWriteFontLookupTableBuilder::QueueShareMemoryRegionWhenReady from separate threads, there may be race conditions around the pending_callbacks_ member of DWriteFontLookupTableBuilder. Sequentialise and guard access to pending_callbacks_ with a separate sequenced task runner. Fixed: 1047054 Change-Id: Ib7d7a385273bd82eb4d1acf720dac5d688a3435e Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2030864 Commit-Queue: Dominik Röttsches <drott@chromium.org> Reviewed-by:Matthew Denton <mpdenton@chromium.org> Auto-Submit: Dominik Röttsches <drott@chromium.org> Cr-Commit-Position: refs/heads/master@{#737252}
Showing
Please register or sign in to comment