It’s surprising that OpenAI hasn’t issued an official response regarding this serious issue. I would have expected at least an acknowledgment of their awareness. This is a very serious problem and could easily cause damage to hardware.
1 Like
I also experience very high CPU usage. It started in the last day or two.
1 Like
I have the same. It doesn’t happen right away and after a few minutes of using chat. I have to refresh the tab every now and then to be able to use chatgpt4 at all because otherwise it crashes the whole browser, so that you can’t even scroll the page.
1 Like
I confirm, that the issue is present, and it is annoying.
1 Like
Getting this issue today. ChatGPT suddenly takes a huge CPU (50 - 60% or more)
Tried in all browsers (Chrome, Firefox, Opera) - Same issue
As soon as I close the ChatGPT tab - CPU usage comes down.
It’s really a dangerous problem (when CPU usage crosses 120+% and temperature rises rapidly for a prolonged period) - and can destroy your CPU or MB. OpenAI - please look into it.
Found this on discord concerning the same issue (see below). But apparently people are still experiencing the problem…
1 Like
Still the same. The longer the browser card is open the more cpu it uses.
Got the same issue on my M1 MBP
leaving the GPT page on Chrome idle for 10 minutes and the CPU usage surges and does not stop on its own. Refresh the page temporarily fix the problem.
Same here. Found via Chrome Task Manager
Same issue… observed up to 150% CPU usage.
Same problem - Windows 11, Opera browser. Page becomes super laggy and unusable after 10 minutes
Here are the troubleshooting I tried with no success:
- Rebooting chrome
- Rebooting my machine
- Clearing cache and cookies
Anyone found a solution?
I monitored performance a couple of times on chrome, most of the time it is completely idle, use doesn’t seem to affect this, re-sampled the performance when my computer started to heat up and this was what I find. this happened randomly, I hadn’t used the tab in maybe 20 minutes and it does not seem to be stopping on its own, I haven’t dug into the JS functions that are being called but it seems to be at least a few different ones. Keep in mind the pie chart of the graph should be almost entirely gray, not yellow, not even making requests will cause this much scripting, my guess is that an infinite loop must be getting initiated somehow, definitely a problem with their website.
2 Likes
Could not understand why Chrome suddenly started overloading some of my CPU threads to 100%. After killing consuming Chrome renderers, I’ve noticed that I had some ChatGPT tabs open - they were taking all my CPU power.
Running M1 Pro Max laptop with Chrome on latest version.
I see that many people have this problem, I don’t believe it’s setup related.
Do they mine crypto with our computers? 
I’m not much for conspiracy theories, but is it possible that ChatGPT uses P2P like structure where clients’ computers are used to perform computations for other clients? 
Is that the reason why OpenAI CEO was fired?
1 Like
even after refreshing it’s still using 200% of my m1 macbook air and causing it to get to 98c
1 Like
Do you think you still have your performance report? Can’t reproduce it directly on my machine. Feels like it’s very random.
1 Like
I tried to poke Michael Schade who works at OpenAI on discord about this issue. I will keep the community posted if he answers.
2 Likes
ChatGPT is consuming like 160% of CPU on my M1 Macbook Pro. This is a serious issue. Can any one at OpenAI acknowledge that and let us know they are working on a fix?
1 Like
This is what a healthy performance graph looks like. just made this one, made a few requests, nothing abnormal going on, at some point the website will begin scripting like crazy resulting in the graph in my first post, you can recreate this by inspecting element and going to the performance tab, this is a chrome feature not sure what other browsers offer, this will let you dig into the JavaScript so if you want you can figure out what the website is actually trying to do, i havent done this yet.
I was affected by this yesterday evening through this morning. After reading Michael Schade’s message via paul_eternallearning, I did a hard refresh, bypassing the cache (Shift+F5 or Ctrl+F5 or similar, depending on your environment), and the behavior has not reappeared for over an hour now.
2 Likes