This is on Macbook Pro M2 and it's making the laptop hot.
#ChatGPT tabs in Chrome started to overuse CPU
ruby jackal
frigid talon
Hey @ruby jackal, thanks for reporting this! We just rolled out a fix. If you refresh, everything should be fast (and stay fast) again!
Sorry for the hassle in the first place—ChatGPT didn't mean to get greedy with your CPU. The underlying issue was a subtle behavior in our frontend app's event handling that would take up more resources the longer the page was open, and in turn slow down things like typing. Now that this specific bug is fixed, we're also looking into some improvements to avoid this kind of problem going forward.
honest cloud
This is fixed, thanks for the fast turnaround
brazen stratus
i still get the same error today in new tabs. it happens after around 30 minutes of having a tab opened. I recorded a stack strace if that may help.
In chrome browser on M1 Mac Pro.
silk fern
for my case, i use Brave browser, Windows OS, but still consumed a lot of CPU resources
honest sapphire
I'm still experiencing the issue. After 10-15 minutes cpu consumption goes from 0 to ~50 and stays there until I close/reload the tab
latent quarry
wow you're right, so that's why lmao
mossy niche
@Michael Schade I still have the same issue.
I tried rebooting chrome, emptying my cache, rebooting my machine, changing browsers and the problem is still there.
Is it possible the issue is still not resolved?
jolly glade
Im also still having the same issue on chrome
slim seal
I also have this issue in both Arc (Chromium) and Safari.
latent quarry
still have them here too
upbeat forge
clearing cookies and relogging in worked for me
vague grail
clearing cookies and relogging in worked for me
Thanks, it works for me now as well.
vague grail
Nope, it worked only partially. The tab doesn't use CPU when it sits in the background, but it does as soon as I come back to it. The app also becomes partially unresponsive. I can type and chat, but I can't switch between chats/GPTs. Routing is basically dead, and it eats up 200% CPU. @frigid talon
upbeat forge
yeah its back for me as well
frigid talon
Hey everyone! Thanks for all the additional detail you've shared, this is all very helpful. We're digging into this as we speak so we can get a fix in at the root and keep you from running into this. Sorry to slow you down—we definitely don't want to be greedy with your CPU cycles.
Please don't go out of your way for this, but if you happen to have specific details on what happened leading up to this situation, we'd appreciate it. How long the tab was open, if you remember what actions you were taking, if you were working across multiple conversations or just one. We'll post an update back here as soon as we know more!
upbeat forge
Not too new of information, but also seeing after switching back to the tab after ~1 hour in the background cpu spikes to 100%
frigid talon
@upbeat forge That happens as soon as you switch back to the tab, or after you interact with the page more?
upbeat forge
immediatly as i switched, all i did was tab back then open inspect
frigid talon
Super helpful, thank you!
frigid talon
By no means do I want anyone to go out of their way for this, but if you're comfortable with Chrome Dev Tools, one thing that'd be incredibly helpful is getting a copy of the app performance profile while you're experiencing this. I'm not sure how doable that will be if the tab CPU usage is maxing out right then, but one or two of these would go a long way. It'd also help us if you can screenshot the console tab so we can confirm any errors populating there.
Instructions on how to generate these are at https://developer.chrome.com/docs/devtools/performance/#record (cc @upbeat forge). Again, please don't burden yourself if you're not comfortable or able, and thanks all for bearing with us—we'll get this sorted out.
upbeat forge
dm'd it
dense ridge
i have the same question, and i don't know whether this screenshot could be helpful
frigid talon
This should be fixed now! You'll need to refresh your tabs that have ChatGPT open to get the latest version.
For some background, we pinpointed this to an issue with our caching layer (which ironically is meant to improve performance), which only manifested for tabs that were left open for awhile when you came back to them from another page or window. We were able to reproduce the issue and so I'm optimistic this fix is it, but given it takes a bit of time to manifest, we'll keep monitoring. (On that note, I wanted to quickly express my gratitude for all of the helpful debugging and input you all shared in this channel—it played a key role in us figuring out how to reproduce it for a faster fix.)
fathom oasis
Now you guys just need to lift the cap please. It's extremely frustrating to only have a few prompts and then having to wait more than 2hrs (in my case) every time. I know it's a load issue, but is there any chance that we will NOT have to worry about hitting some limit in the future. It's especially bad trying to debug our Gpts. The limit is even lower on them.
frigid talon
Now you guys just need to lift the cap please. It's extremely frustrating to onl...
We don't like them either 🙂 Top of mind for us!
slim seal
I can confirm this is fixed for me. Thanks!