Fixes a deadlock between shouldInterceptRequest() and getCookie()
In the WebView shouldInterceptRequest is called on the IO thread. The CookieManager used to post cookie monster tasks to a thread which was sometimes the IO thread (if the WebView was started before the CookieManager) but sometimes a special thread (if the CookieManager was started before the WebView). getCookie is synchronous and blocks waiting for the result after posting its task so if getCookie was called from shouldInterceptRequest and the cookie monster was on the IO thread then it deadlocked. We fix this by always starting the special thread for the cookie monster. Android Issue: https://code.google.com/p/android/issues/detail?id=65786 BUG=374203 Review URL: https://codereview.chromium.org/284313005 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@271715 0039d316-1c4b-4281-b951-d872f2087c98
Showing
Please register or sign in to comment