Use a ThreadChecker in DeviceSensorHost instead of DCHECK_CURRENTLY_ON.
BrowserThreads forget their identity during shutdown, causing nonsensical errors like "Check failed: ::content::BrowserThread::CurrentlyOn(BrowserThread::IO). Must be called on Chrome_IOThread; actually called on Chrome_IOThread." if DCHECK_CURRENTLY_ON is used in something that is called from a MessageLoop shutdown observer. This CL fixes this problem in DeviceSensorHost by using a ThreadChecker instead. BUG=625988 Review-Url: https://codereview.chromium.org/2160913005 Cr-Commit-Position: refs/heads/master@{#406995}
Showing
Please register or sign in to comment