The Google Chat memory leak case with Chrome DevTools MCP, and the Chrome Dev channel update. Both checked against the official posts.
These are the two official announcements checked in web this week: the Google Chat team's case study with Chrome DevTools MCP, and a Chrome Dev channel update. Both were opened at the source to confirm the date and content.
| Chrome DevTools MCP | October 29 | How the Google Chat team fixed 30+ memory leaks |
| Chrome Dev channel | October 30 | The Dev channel moved to 159.0.8130.0 |
- Chrome for DevelopersChrome DevTools MCP case study (opens in a new tab)How the Google Chat team found memory leaks with an agent
- Chrome ReleasesChrome Dev update (opens in a new tab)Dev channel release notice
Finding memory leaks with Chrome DevTools MCP (October 29). The Google Chat team connected the memory tools of Chrome DevTools MCP to an agent, had it analyze a heap snapshot, and says it landed 30+ fixes. The snapshot was about 500 MB, and the team recorded it by hand before giving it to the agent. The biggest find was an error object. One error constant (EMPTY_KEY_ERROR) created when a module loaded retained 14.1 MB, and all the pre-allocated errors together held about 20 MB. An error captures the call stack when it is created, so that stack kept the app's initialization code alive. Creating the error where it is thrown fixes it.
The window had 1,142 event listeners, 128 of them on window. 126 of those came from timestamp components such as "5 minutes ago", each registering its own visibilitychange. A shared service now registers one, so 126 became 1. The post says the agent itself noted this was a scale problem, not a true leak. More than 27 other leaks were fixed too, and the total is described as hundreds of MB, with no per-fix numbers.
Image: Chrome for Developers
My reading: if you run a web app that stays open for days, this procedure is worth trying. But 30+ is one app's result, and I did not find an independent reproduction, so it does not mean you will find as many.
Chrome Dev channel update (October 30). The Chrome team moved the Dev channel on Windows, Mac and Linux to 159.0.8130.0. It is a Dev channel build, not a stable release, so it does not mean a new web feature reaches stable. Treat it as an early look for regression checks.
The two items carry quite different weight. The Google Chat case publishes both its numbers and its procedure, so a team with a long-lived web app can try it. The Dev channel update is better read as "this is coming". That is my interpretation.
- How Google Chat fixed 30+ memory issues with Chrome DevTools for agents, Chrome for Developers
- Chrome Dev for Desktop Update, Chrome Releases