[mojo] Fix data race on NodeChannel destruction
See bug for details. It's possible for the IO thread to unsafely access a NodeChannel after it's been destroyed on the UI thread. This fixes the issue by ensuring the NodeChannel is always destroyed on the IO thread. Fixed: 1081874 Change-Id: I1fc4eaa0cef20f036c85fee3ed7976f518fbf60e Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2357451 Commit-Queue: Robert Sesek <rsesek@chromium.org> Reviewed-by:Robert Sesek <rsesek@chromium.org> Auto-Submit: Ken Rockot <rockot@google.com> Cr-Commit-Position: refs/heads/master@{#798795}
Showing
Please register or sign in to comment