Opera Browser: GPU process consuming lot of CPU
-
cratte last edited by
My Opera Browser runs high on CPU usage after a while since a week. All restarting useless.
The GPU-Process as to see in the task manager per Shift+ESC is the second most eater after Opera itself.My suspicion: Facebook eats all CPU power.
I open mostly FB pages and after 20 minutes with opening and closing and reopening serveral FB pages Opera behaves strange and does not load all FB pages but stucks in trying to... -
cratte last edited by
@cratte
Also the process "Renderer" now uses too much CPU%
I have to kill it too to get some stressless time
Screenshot:
https://i.ibb.co/TBnzcrn/Opera-Browser-too-high-CPU-Renderer-kill-2020-10-28-184639.jpg -
DearMadelene last edited by
Same proiblem, it is not possible to use browser when everything is so slow and twitchy. Only yesterday all was fine! Really frustrating, all my bookmarks, open pages and passwords in Opera, which right now almost not possible to use because of this issue.
-
cratte last edited by
@DearMadelene use the Opera built in task manager as described and kill the CPU burner - BUT be careful: them are GPU process and sometimes "Renderer".
Try it. -
cratte last edited by leocg
This topic is modern and gets not old like the forum algo wants to tell us.
Memory consumption will never get solved.My solutin, workaround against RAM loss with Opera and all Chrome Browsers:
Kill the renderer processes.
This brutal method shows no negative effects the last months for me.
Positive: Memory gain
Renderer processes appear and grow for every new tab, read below.This is my method, use at your own risk!
"Memory Usage Backgrounder.
Chromium Memory Usage.
Here is some background information if you are measuring memory in Chromium.
Multi-Process Model Background.
To understand Chromium's memory usage, let's understand the multi-process model. Unlike other browsers, Chromium is divided into multiple processes.
When Chromium starts up, it will initially have two processes. One process is the browser process which controls the main browser functionality, and the other is the initial renderer process, which runs the Blink rendering engine and JavaScript (V8).
Each time you open a new tab in Chromium, you'll likely get a new renderer process. With typical browsing, it is common to see 5-7 chrome.exe processes active.
Further, if you utilize plugins, apps, or extensions, they may also execute within independent processes.
https://www.chromium.org/developers/memory-usage-backgrounder
