canvas2d: Don't access Thread in CanvasResource dtor.
There is no ordering guarentee in the destruction order for objects in thread local storage. Since Thread and SharedGpuContext are both in thread local storage and destruction of CanvasResource can be triggered by SharedGpuContext being destroyed, we shouldn't access Thread in the CanvasResource dtor since it may have already been destroyed. R=fserb@chromium.org Change-Id: Id7efe3eb51fa242382f7446b731f0531c6bd9816 Bug: 1002792 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1799223 Auto-Submit: Khushal <khushalsagar@chromium.org> Commit-Queue: Fernando Serboncini <fserb@chromium.org> Reviewed-by:Fernando Serboncini <fserb@chromium.org> Cr-Commit-Position: refs/heads/master@{#696023}
Showing
Please register or sign in to comment