Public bug reported: We currently create and initialize the cookie store on the UI thread because it's required to make the UI thread cookie store proxy immediately available to the CookieManager API. However, the cookie store really lives on and is used on the IO thread, and net::CookieStore is not thread safe. Whilst it's sort-of ok for the time being (we guarantee there aren't any concurrent accesses during initialization), this will break if Chromium modifies net::CookieMonster to assert that it's called from a single thread.
** Affects: oxide Importance: High Assignee: Chris Coulson (chrisccoulson) Status: Triaged ** Changed in: oxide Importance: Undecided => High ** Changed in: oxide Status: New => Triaged -- You received this bug notification because you are a member of Ubuntu WebApps bug tracking, which is subscribed to Oxide. https://bugs.launchpad.net/bugs/1560271 Title: Cookie store should be created and initialized on the IO thread Status in Oxide: Triaged Bug description: We currently create and initialize the cookie store on the UI thread because it's required to make the UI thread cookie store proxy immediately available to the CookieManager API. However, the cookie store really lives on and is used on the IO thread, and net::CookieStore is not thread safe. Whilst it's sort-of ok for the time being (we guarantee there aren't any concurrent accesses during initialization), this will break if Chromium modifies net::CookieMonster to assert that it's called from a single thread. To manage notifications about this bug go to: https://bugs.launchpad.net/oxide/+bug/1560271/+subscriptions -- Mailing list: https://launchpad.net/~ubuntu-webapps-bugs Post to : ubuntu-webapps-bugs@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-webapps-bugs More help : https://help.launchpad.net/ListHelp