[VB-80821] Memory leak on latest Vivaldi
@antrax666 Intel i5... I've confirmed (to my satisfaction ) that when Vivaldi starts using ~12 GB (that's Giga Bytes, folks! ) it all but shuts my system down.
(I've watched it jump from < 3 GB to almost 13 GB, with no change of state: No additional tabs or windows, no activity other than scroll a page while reading...)
Quitting Vivaldi brings my system back to a usable state; and relaunching Vivaldi "cures" the — I presume it's a leak...
My CPU often runs at ~160º F, so my "experience" may not be typical!? (Please note: This machine has had problems due to over-heating long before I installed Vivaldi... It may -indeed- be "a notorious design flaw in the Mac mini" itself.)
AntraX666 last edited by AntraX666
I also have Intel. Luckily for me Vivaldi never took down MacOS, just it self.
I dont close the Vivaldi when Browser process is huge, because that will freeze my system when its managing the huge RAM consumption from swap to properly shut down. When it crash, its instantly empty and I can ran new instance way faster, just annoyingly it crash always when you dont need it...
Regarding the high temperature, my Air goes crazy too when I try to close Vivaldi properly and Browser process is over 10GB, but CPU is going crazy always when there is high memory pressure and there is reallocation of memory.
If I ever have chance to play with Mac with M1, will test Vivaldi there if this bug is present also on M1 or just on Intel CPUs.
@antrax666 Tomorrow I'm going to put a new fan into my machine... Fingers crossed!
But memory usage shouldn't spike like that: Something somewhere is allocating RAM for no good reason; and the app isn't monitoring it...and obviously not releasing it when it should!
Classic C-type language memory glitch: Probably a simple array pointer gone "rogue"!
Hi all, it is very noticeable when I edit anything in confluence, even the input of characters slows down, while htop shows that the Vivaldi Framework uses 70% of the cpu.
MacBook Air M1, macOS Monterey 12.3.1
Vivaldi: 5.2.2623.41 (Stable channel) (arm64)
@oakdaleftl Good luck with fan replacement, shouldn't be hard to swap.
I am not sure but Browser process I think is responsible for all data handling and it just doesn't throw old data away and keeps them allocated. In activity monitor real memory usage is normal but memory usage is this crazy thing (if I understand it right, memory usage is allocated memory space, which seems to be limited to 64GB, and real memory usage is what is actually used?).
RuninGag last edited by
@AntraX666 Memory usage (under the Chrome model) is bizarre — but the spikes to >12 GB are obvious signs that something is wrong...
I always run (at least) two profiles, and the synced profile's main window routinely sneaks up to over 200 tabs; which has never been a problem, before. (You should see the Window menu try to populate its favicons! ) This is something new with 5.2...
@RuninGag I know how Chromium browsers behave, they are RAM needy, I would be fine with that, because you can always kill process which eats too much of RAM except the Browser process
The memory leak I first notice on Vivaldi 3.8, it was same till 5.something then Browser process started to crash reaching 15GB of RAM. So thats at least some change (to worse but change). Unfortunately Vivaldi on Mac seems pretty minor and I dont have Linux to test it there, my hope is it will get randomly fixed as it was randomly broken
By fav icons you mean icons for tabs? With that I dont have problem even 300+ tabs, what I share across platforms with 200+ tabs is that any audio freeze Vivaldi for moment, but I experience that from 3.5 so when I need audio or video with audio I know I have to keep tabs under 150.
Chas4 last edited by
I do know some sites cause browsers to eat more RAM, check with the Vivaldi task manager and see if you can track down which ones trigger the spike.
@Chas4 Tried that done that. If site consume more RAM you can see it in manager which site eats how much of RAM, but when Browser process grows, you have no clue why. Fastest way to make Browser process grow is browsing "infinite" scrolling sites (9gag is good for that) and leave some sites which dynamically redraw graphs. With this combination I can kill Browser task in less than 24 hours.
All you can change is the pace of growing of the Browser process, but it grows all the time Vivaldi is open.
And yes closing all tabs and task wont make Browser process any smaller.
Vivaldi on Mac seems pretty minor
What I've routinely noticed is that < 4 GB is well-behaved. Past 5 GB it'll head upwards of 12 GB (and beyond, if you let it...?). And it shows in terms of performance.
I've managed to overcome my reticence: When I note a blip in the trajectory, I quit Vivaldi and re-launch; it works and it's quite painless!
I've not found any rhyme or reason for the blip... My main window is a mere 225 tabs, so it can't be that! (?? ) Seriously, Vivaldi's browsers easily accommodate tab hoarding...
Is it a bug? Certainly. Is it a real problem -for me? No. Not really. But it would be nice to swat this one!
A more serious "happening" is the hang-on-right-click gremlin... Muscle memory makes it annoying!
Okay, latest Vivaldi and so far all same, memory leak still present and crashing when Browser process hoards over 16GB of memory space. I can crash Vivaldi in 4 hours if I will open and close many tabs. Kinda miss the times when it just grew up to 60GB and ran out of memory space and system told me, hey close something or bad things will happen.