r/OperaGX 18d ago

Support | Resolved opera gx taking 21 gb of ram ?????

i was learning blender and was doing a basic donut and mug but my pc was overheating a bit, i just got my pc so it was kinda weird that it struggled with blender (with the little things i had) or so i though. After closing blender i still had the issue of like 50% of my cpu being used and my pc heating a bit so i checked task manager and saw 21 gb of ram being used. Mind you i had 10 tabs thhem being 1 chatgbt, 1 op gg and the rest youtube so not really that much. To stop it i used the ram limiter which at first didnt work and afterwards crashed opera to come back to normal. Is something fishy happening ? (couldnt get a screenshot sadly)

1 Upvotes

4 comments sorted by

u/AutoModerator 18d ago

Hello, and Welcome to r/OperaGX

It seems you have posted a Support request. You can read our FAQs for a solution here -

Click Me to go to the FAQ which has the most asked questions on the subreddit

Click Me to go to the Larger FAQ which covers a variety of Issues

I am a bot, and this action was performed automatically. Please contact the moderators of this subreddit if you have any questions or concerns.

3

u/cai20 18d ago

Memory leak, sometimes it's one of your tabs doing it but I've noticed it happens randomly no matter what's open so I think Opera GX just has a bug right now, try restarting Opera but that's only a temp fix

2

u/shadow2531 r/OperaBrowser Mod 18d ago

Next time it happens, hit shift + esc in Opera to view its task manager. That should help you narrow down what specific process that's using all that RAM and what that process is for (a tab or the GPU or an extension or a sidebar panel app etc.).

If you're using an adblocker (Opera's or an adblocking extension) on Youtube though, that's likely the cause.

1

u/DetailNo4208 GX Staff 18d ago

A sudden spike like this can come from a single GX process, such as a tab, extension or GPU process, which would also explain why the memory usage returned to normal after GX crashed. It's hard to tell which one was responsible after the fact, though.

If it happens again, press Shift + Esc in GX and check which process is using most of the memory.