Memory leak in Vivaldi?
-
I've noticed that when I leave some tabs open for more than a day or so, e.g. Slack, Google Drive, Twitter, that the "Browser" process grows in memory to 1gb or more. When I hibernate these tabs, the "Browser" process never shrinks again. Even if I completely close all those tabs -- so that there's just one blank tab left -- the process still holds onto 900mb or so. Is this a memory leak? Is there a way to get Vivaldi to free up the memory from the "Browser" process?
-
What version of Vivaldi, what macOS version and any extensions?
-
Vivaldi: 3.2.1967.41 (Stable channel) (64-bit)
OS X: macOS Version 10.14.6 (Build 18G6020)This computer has 4gb of ram and it's a Macbook Air so it's not something I can upgrade.
Extensions: Ghostery, Google Docs Offline, Page Ruler Redux
Thanks Chas4!
-
I just disabled every extension and closed every tab, after running Vivaldi all day, and this is what the task manager looks like. It was also very sluggish until I restarted Vivaldi entirely, and now everything is snappy again.
-
Any difference with todays (8/19) Vivaldi update to 3.2.1967.47? Also have you restarted the computer in a while?
In Vivaldi Settings under Appearance does turning off Use Animation help?
-
I am on the latest version, 3.2.1967.47. I have restarted the computer recently.
I just disabled animations and I will restart Vivaldi and run it for a day and see if it still behaves like this.
-
I disabled animations, disabled extensions, restarted Vivaldi and my computer, and then ran Vivaldi for a day or so.
Memory use swelled up to 1+gb, so I closed every tab and this is what it's like now:
-
This current version has been pretty bad leakage-wise (at least in 10.13). I been giving it a restart before it ever got to a GB. But usually after a day, it's running at 700mb (after starting at 95-100mb).
To be honest, every version since 3.0 has leaked a little. But for whatever reason, this particular version has been pretty bad.
-
@Gwen-Dragon Hi Gwen-Dragon, thanks for responding.
Ghostery is currently disabled, and I have had it disabled ever since Vivaldi came out with its own tracker blocking.
If the extension is disabled but not removed, would that still cause this problem? I would have thought that a disabled extension wouldn't ever have its code executed (i.e. in such a way that it could cause leaks).
-