Google is working on Chrome updates with no restart requirement, a change meant to make browser security fixes less dependent on users clicking the relaunch button at the right time. In a Thursday post, Google said it is investing in dynamic patching for Chrome so some updates can be applied without a full browser restart.
The work comes as Google says AI-powered security tools are finding and helping fix more flaws in Chrome. According to Google, Chrome 149 and Chrome 150 included 1,072 bug fixes, a count the company said is higher than the total number of patches across the previous 23 major Chrome releases combined. That is a lot of plumbing to ship through a browser people tend to leave open for days because their tabs are apparently load-bearing infrastructure.
Google has already said Chrome will move to a two-week release cycle starting in September, with security updates arriving between those larger releases. The company also said it is weighing two security updates per week in response to what it called fast-moving AI-powered attacks.
Will Chrome updates need a restart?
For now, yes, many Chrome updates still require a browser restart before the new code is actually running. Google’s stated goal is to reduce that disruption through dynamic patching, though the company has not said when the restart-free update work will ship broadly or which kinds of fixes it will cover.
Dynamic patching, as Google described it, is aimed at shifting more of the update burden away from the person using the browser. The security reason is straightforward: a downloaded update does not protect anyone if the vulnerable version is still running in memory.
Google tied the effort to a specific class of risk known as N-day attacks. An N-day attack targets a vulnerability after a fix has been released, betting that many machines have not installed or activated the patch yet. Once attackers can study a public fix, lagging users become easier targets.
What Google is changing first
Google said it is also looking for moments when Chrome can restart itself without making a mess of the user’s session. The company framed that as automatic restarting only when it can preserve the session cleanly, rather than dumping someone back into a half-remembered pile of tabs.
One version of that approach has already appeared in Chrome 150 on macOS, according to Google. On Apple’s desktop operating system, applications often keep running in the background after all visible windows are closed. Google said Chrome can use that state to perform a restart with less obvious interruption.
The pieces Google described point to a browser update model with two tracks:
- More frequent Chrome security releases, including the coming two-week browser cycle and possible twice-weekly security updates.
- Less visible activation of fixes, through dynamic patching and carefully timed restarts where session restore can be preserved.
Google’s post does not turn dynamic patching into a shipped, universal Chrome feature today. It does show where the company thinks the browser update problem is heading: more bugs found faster, more patches shipped faster, and less patience for asking users to do the boring but necessary part manually.
This story draws on original reporting from The Verge.
