Let service worker and navigations use the same process from Android's NTP.
Android's New Tab Page has an empty site URL by design to let navigations from the NTP use the same process. The site URL is assigned after the navigation is committed. However, this doesn't interact well with SW. SW is created in a process suitable for the service worker's script URL, and the navigation stays in the NTP process, so the SW is out-of-process which has a performance and memory cost. With this CL, when the SW process is chosen, it takes a process that hasn't yet been assigned to a SiteInstance. The idea is to choose the Android NTP process. Bug: 1012143 Change-Id: I423de186982a11c68e4c2bec7b5ca56b3245f62c Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1849473 Commit-Queue: Matt Falkenhagen <falken@chromium.org> Reviewed-by:Alex Moshchuk <alexmos@chromium.org> Cr-Commit-Position: refs/heads/master@{#707274}
Showing
Please register or sign in to comment