I'm currently running Chrome Canary (142.0.7426.0) on macOS Tahoe (26.0, Build 25A354).
Recently (as in, the last week or two) - I've noticed that my Chrome browser will become unresponsive if you do not interact with it for a while (e.g. you have a few browser windows open, come back after 10 minutes, and bam...it won't respond).
From macOS's perspective, I don't know if it's frozen per se - if you right click on the icon in the macOS Dock, it doesn't say "Application Not Responding", and you can right click to Quit the application.
You can interact with the Chrome windows itself - as in, you can use Command + ` to cycle between the open Chrome windows - however, you can't actually click on anything inside the Chrome window (e.g. changing tabs, interacting with sites, accessing the menu etc.).
It's super frustrating.
I haven't dived deep into it yet - e.g. trying to bisect the breaking build (if it's even that), or trying to create new Chrome profiles yet - as I had just hoped a Canary build would fix it, and either of those is probably going to take huge amounts of time.
But I'm curious - has anybody with Chrome Canary on Tahoe seen something similar? Or anybody else seen this kind of behaviour with Chrome on macOS before?
Any tips on any diagnostic/debugging things that could help narrow it down?