See https://chromium.googlesource.com/chromium/src/+/077ae35f3269e419e7119d4dd6495a00d65ac4d6
GrapheneOS/os-issue-tracker#7829 (comment) goes over how an app using Google Mobile Ads SDK can deadlock when the remote Dynamite ad module is not available (e.g. a user without sandboxed Play services installed installing apps from Aurora Store or APK mirroring sites, or an issue in Play services). Trying to install the app from the issue without Play services install results in the app ANRing on launch.
Essentially, the worker thread blocks on a posted task to main thread to initialize WebView, but the main thread can be blocked on the lock that the worker thread is holding. Enabling this feature would workaround this deadlock, as it won't have the worker thread wait for main thread to do anything.
See https://chromium.googlesource.com/chromium/src/+/077ae35f3269e419e7119d4dd6495a00d65ac4d6
GrapheneOS/os-issue-tracker#7829 (comment) goes over how an app using Google Mobile Ads SDK can deadlock when the remote Dynamite ad module is not available (e.g. a user without sandboxed Play services installed installing apps from Aurora Store or APK mirroring sites, or an issue in Play services). Trying to install the app from the issue without Play services install results in the app ANRing on launch.
Essentially, the worker thread blocks on a posted task to main thread to initialize WebView, but the main thread can be blocked on the lock that the worker thread is holding. Enabling this feature would workaround this deadlock, as it won't have the worker thread wait for main thread to do anything.