G
@xyzzy said in Practical ways to get Vivaldi to use less RAM/disk:
@GrantJacobs Have you tried disabling ALL of your extensions (to see if that makes any difference) and then re-enabling them one-by-one? I know that you need all of your extensions for your work but if this turns out to be an extensions-related issue, you can file a bug and the Vivaldi team can then hopefully replicate it and resolve it.
I thought of this, but am a bit busy ATM. Will try later.
I'm aware of hibernating tabs / stacks. They sound promising, although the help blog isn't clear as to precisely what hibernating does. It gives an Apple-speak like "uses less resources".
Vivaldi's "Tab Hibernation" takes advantage of Chromium's Tab Discarding to reduce Vivaldi's memory footprint when a user has many tabs open. (That Google blog post is old, but it gives a nice summary.) Vivaldi's "Lazy Load" feature also places tabs into a "discarded" state when you launch Vivaldi and resume your last session.
Thanks for the link, will read later. Will try to look for info on what 'Background Page: Vivaldi' is later, too.
FWIW, there's an irony in all of this. (*For me, anyway.) The blog post on how to manage memory in Vivaldi says to keep an eye on processes that increase in RAM over time (i.e. might be leaking). The only ones that do for me are Vivaldi ones… The pages and extensions stay more-or-less sane, if on the large size for many pages. But even the GPU process creeps up, from ~20+ Mb to ~120. And the 'Browser' process gets huge. 'Background Page: Vivaldi' is big, but doesn't seem (subjective observation!) to grow as fast. These seem to be the thing that knocking Vivaldi over and restarting "fixes".
Maybe it's just that Chromium having grabbed some memory for something just doesn't like releasing it? 'Browser' and 'Background Page: Vivaldi' only slightly reduce if hibernate all background tabs. They're still at ~700Mb and ~300Mb, respectively.
