The web version of ChatGPT keeps crashing

4o (which I like and find extremely useful for my GPTs thanks to the longer outputs) has been out for a while now, and I’ve probably already generated thousands of outputs with it with very few issues.

The constant crashes only started in the past couple of days, so it’s not the 4o rollout that caused it, but some other, more recent update.

1 Like

Memory usage reaches incredible levels, the browser freezes and crashes, the problem continues in different browsers, completely deleting the chat history or clearing the browser cache does not work, after a few chats the RAM increases again, this problem started yesterday for me, I was using it without any problems before.

2 Likes

I am experiencing browser freezing and crashing due to high RAM usage. This problem started yesterday. It continues even though I cleared the cache and deleted all chat history and tried different browsers.

Please fix this issue. I’m running on a non-M Apple and do not have the option to use the Desktop App. The web UI is crashing all browsers.

Try Mac desktop app. Some say it is not afflicted by the bug. I don’t have a Mac, so I must keep starting new conversations.
Btw it’s been reported here by many:

Desktop App only works on M1 or newer Macs

This is at best a temporary solution.

There is a serious bug in the client side scripts.
open AI is running server side not on the client.
To output a 1 or 2 pages of info, 4gb of memory is required ?
many of those settings i dont want to change. Chatgtp isnt the only thing a browser is used for.

Expected Behavior:

When I open ChatGPT within a Firefox or Chromium browser, I should be able to use all of the features and prompt ChatGPT. I should be getting the typical response time from ChatGPT. No heavy resource usage should be necessary on the client-side.

Current Behavior:

Every time I prompt ChatGPT from Firefox or Chromium, my CPU cycles crank up to 100%, my fans kick into the highest speed, and my CPU temps reach upwards of 85 Celcius. ChatGPT tabs are also taking up an enormous amount of RAM.

The tab will reliably crash before ChatGPT has finished its response. When I open a new tab and re-visit that thread, the response is complete. If I prompt it again, the same thing will happen again.

What I have tried:

  • Testing on multiple browsers.
  • Clearing cache
  • Clearing cookies
  • Resetting each browser to its default settings.

Concerns:

Your web app shouldn’t be crashing tabs on ANY browser. My CPU should never cycle like that because of a web page.

Comments:

Someone pushed a major bug to production that has clearly been here for days with no word from the OpenAI team. For a so widely used app, this behavior is unacceptable and I am now considering ending my subscription in favor truly free and open source alternatives.

Specs:

  • CPU: AMD Ryzen 9 7940HS w/ Radeon 780M Graphics (16 cores)
  • GPU: GPU: AMD ATI Radeon RX 7700S/7600/7600S/7600M XT/PRO
  • RAM: 64GB
  • OS: Arch Linux x86_64
  • Browsers:
    • Firefox 127.0b5 (64-bit)
    • Chromium 125.0.6422.112
1 Like

For example, Gemini uses between 75-180 MB of RAM and it does not increase no matter how many chats are opened.

Dear OpenAI: Can you pls have a Beta option instead of throwing everyone around like ragdolls.

2 Likes

it started happening yesterday for me, I’m in NA-EAST region. 16 gb ram, but the ram usage goes so high randomly while waiting for a prompt answer, and freezes the whole browser (google chrome, windows 11). I use chat gpt 4o every single day for coding tasks so when I say it happened yesterday, I hope you can spot where you sent a regional update. I’m also using chat gpt teams, not the chat gpt plus.

Experiencing the same issue, granted I have 64GB of RAM on my PC so it takes more than 2-3 gens, but it is absolutely crashing once every couple of hours or so of constant use.

Hello, the memory leak is caused by too many event listeners attached by highlight.js to the window object, around 3K per chat.
For preventing this you can block adding more event handlers to the window object

Could you tell me how to to do it?

I can’t paste links here, but if you are familiar with devtools you can use this:

window.original = window.addEventListener;

window.addEventListener = function (type, listener, options) {
  if (type === "DOMContentLoaded") {
    console.warn(
      "Adding new DOMContentLoaded event listeners has been blocked."
    );

    return;
  }

  window.original.call(window, type, listener, options);
};

5 Likes

Same here. 64GB and this thing is crashing over and over.

It doesn’t help that the new version is so damn verbose. STFU once in a while. I ask question which could be answered in a single sentence and get 30 pages of response.

2 Likes

Though it was me. I am having the same problem. It is running out of memory and it’s crashing a lot.

2 Likes

Nice to know it’s not just me.

It’s rather annoying, especially when it does it half way through a text generation.

1 Like

unfortunately the problem persists

1 Like

I first experienced this error 3 days ago. Since then, it keeps recurring after 2-3 responses.

1 Like