Ensures BluetoothAdapterWinrt initialisation runs on foreground thread
PerformSlowInitTasks should be scheduled (BEST_EFFORT) but once it starts executing it needs to be on a foreground thread to avoid priority inversion. From this crash/312ca3b6fb0c2131 Thread 28 ThreadPoolBackgroundWorker LoadLibraryExW [...] RoGetActivationFactory device::BluetoothAdapterWinrt::PerformSlowInitTasks() [...] base::internal::WorkerThread::RunBackgroundPooledWorker() This is blocking other threads. R=joenotcharles@google.com Bug: 973868 Change-Id: Ic7512ad567bc4e3a5fc549dd9c408db0047a45fc Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2377904Reviewed-by:Joe Mason <joenotcharles@chromium.org> Reviewed-by:
Reilly Grant <reillyg@chromium.org> Commit-Queue: Etienne Bergeron <etienneb@chromium.org> Cr-Commit-Position: refs/heads/master@{#802019}
Showing
Please register or sign in to comment