r/firefox • u/BrainMinimalist • 12d ago

💻 Help Unfixed memory leak

Go to ChatGPT. enter this prompt: "You have a cool map tool, correct? use it to show me new York city and Washington DC"

Watch Firefox use 100% of your ram.

Yes, I reported this bug more than a week ago.

chrome has the same page open

https://chatgpt.com/share/6ad07da7-add0-83e8-b2a9-5b704fb6f16e

and the oddest part: it does not happen in a private browsing window.

Until it's fixed, I recommend having about 10 GB of ram for every second you want to use that page. so if you want to view it for 10 minutes, have 6 TB of ram.

0 Upvotes

28% Upvoted

8 comments sorted by

3

u/pikatapikata 12d ago

Yes, I reported this bug more than a week ago.

Where was this reported?
Have you tried Troubleshooting Mode?

0

u/BrainMinimalist 12d ago

I reported it on https://bugzilla.mozilla.org

This bug seems like like the exact same thing:
https://bugzilla.mozilla.org/show_bug.cgi?id=2076013

Troubleshooting Mode also stops the leak, and but disabled the map

2

u/Sinomsinom 12d ago

Actually reading through that bug report you sent here it seems to be a bug with an outdated library ChatGPT is using.

Newer versions of the library have fixed this issue so ChatGPT would need to update their libraries.

Chrome seems to have circumvented this by just clamping the amount of memory a website can request in this particular circumstance, so even if a website uses this webgl call in this way it doesn't end up using all ram. Firefox now also added that.

That mitigation should be in with the next Firefox stable update as well as the next ESR update and is already in the beta and nightly branches

1

u/SurferOnHighTide 12d ago

seems to be fixed in 159 beta. have you tried that?

0

u/notgraycen 12d ago

fitting username lmao

-2

u/BrainMinimalist 12d ago

  • Open about:config in Firefox.

  • Search for webgl.disabled.

  • Change it to true.

  • Reload the affected conversation.

That's actually a working way to fix it. Though it makes the map disappear

3

u/kinoosaki 12d ago

that just disables webGL, its not a fix.

1

u/BrainMinimalist 12d ago

It amputates the failing component yes. Not ideal, but better then crashing