Infinite RAM usage
-
I have the same problem.
Since it updated to 1.1.1077.41 it seems to have some kind of memory leak. I also have seen it to consume all of the available RAM (14 out of 16GB) which made Vivaldi unresponsive and the rest of my System (Kubuntu 14.04) very slow.
I can't tell what triggers the memory leak. I have seen it happening seconds after I start Vivaldi but sometimes it goes well for a couple of minutes, maybe even more.
Hadn't had time for much testing since I only updated this morning and haven't been in the office the whole day. -
Furthering my post on Saturday above...
Yesterday I experienced exactly what
jkierzkowski
wrote:After some time (from few seconds to about an hour) the "Browser" process (as seen in the Vivaldi task manager) starts to use more and more RAM quickly, until all RAM and swap space ends.
At one point, after killing all Vivaldi processes because closing the program conventionally left some vivaldi-bin zombie processes, when restarting Vivaldi it immediately started the RAM grab, in my system monitor I watched the main process growing until it reached 14.6 GB (no more RAM was available). I restarted it and it did the same thing again. I restarted again and it was fine for an hour or two until the RAM grab began again. This morning I've had Vivaldi open for nearly two hours with no problems at all.
OS: GNU/Linux x86_64 Kernel: 3.13.0-24-generic Distro: Linux Mint 17 Qiana, Cinnamon 64-bit 2.2.16 [Based On: Ubuntu 14.04.5 LTS, Trusty Tahr]
-
Am I wrong or do all the people that reported this issue so far have a Ubuntu 14.04 based distro?
(Btw: Right now I have vivaldi open for about an hour without the memory leak.)
-
@b00nish
Yes, you are wrong. I am using Manjaro Linux (based on Arch Linux). -
I've linked a screen capture video of my Linux System Monitor showing Vivaldi grabbing all available RAM in real time. Approx. 2 mins after Vivaldi is started it starts aggressively taking RAM, hitting 1 GB after about 2.5 mins, 10 GB after 7.5 mins, and 14 GB after 11 mins. It maxes out at 14.4 GB, which I'm fairly confident is all the RAM that was available at the time on my 16 GB system, at that point my desktop was getting so slow to respond and I killed the Vivaldi processes.
Here is the link to the VivaldiSysMonVidCap.webm video. Apologies for the poor quality, desktop background keeps flashing, clearly my screen cast settings need some tweaking.
Note: 3 Vivaldi windows were open; Window #1 had 4 open tabs, Window #2 had 6 open tabs, Window #3 was in use and had 6-12 open tabs. None of the tabs were playing video or audio.
OS: GNU/Linux x86_64 Kernel: 3.13.0-24-generic Distro: Linux Mint 17 Qiana, Cinnamon 64-bit 2.2.16 [Based On: Ubuntu 14.04.5 LTS, Trusty Tahr]
-
@b00nish
I'm using Arch Linux. -
Unlikely but possible... Could Cinnamon be in use by all?
-
@mattst I use Plasma 5.11.5
-
Just for general comparison [seems little different to me to pretty much all my prior V versions] - i make no judgement here of good or bad; it just "is".
Btw, the highlighted process has no special significance; i merely forgot to move my cursor before the shot.
-
There is a load of bug reports in the bug tracker about exploding RAM and it is not only a Linux problem, other platforms get hit by it too. So far there are no reliable steps how to reproduce it reliably.
I personally was hit once on two of my computers, both times that hefty that it wan't even possible to get a decent log of any kind out of it. On one of the computers had not even extensions installed, it was basically a fresh profile with a bunch of tabs open when suddenly everything exploded into my face so that I had to kill the browser. Now the sad thing: It never happened to me again, I couldn't repeat it with the same session, settings etc.
One of the users who got hit more or less regularly managed to get a stack trace, but even that was not helpful so far.
It is really becoming desperate by now, any hints or exact steps how to reproduce it reliably are highly welcome. -
@quhno I can reproduce it almost on demand. I only don't know how can I help more.
It seems the problem occurs after opening a new tab.
But how can I enter a debug-mode, or so, to give any stack trace?
What else can I do? -
I just made another test.
I installed vivaldi-snapshot, copied ~/.config/vivaldi to ~/.config/vivaldi-snapshot and run the snapshot version. And I couldn't reproduce the bug then.
I run vivaldi-stable again. Opening a new tab caused the problem again. -
Now, after few hours, the snapshot version does the sameβ¦
-
You guys should simply download more RAM.
-
@luetage omg cewl, what if i want 16 more gigz? should I click 16 times?
-
@luetage Damn, I wish I knew that earlier!
But Vivaldi 1.14 consumes infinite amount of RAM. Can I download infinite amount of RAM in a finite time? -
@ian-coog Just select the 16 GB plan!
-
This morning I received a new version (1.14.1077.45) via the updater. Unfortunately it doesn't solve the problem. Vivaldi still eats up all available RAM. At least form time to time.
-
I left my memory monitor on this morning and when Vivaldi started aggressively taking RAM I started the
strace
program with the ID of the Vivaldi process that was taking the RAM. When I startedstrace
the process was already 6.5 GB and I let it run until it maxed out at about 13.5 GB. With my system running slowly, I exited Vivaldi without killing it using Ctrl+Q, it took a couple of minutes for all the processes to end, but it did exit cleanly (I thought that might help with thestrace
data).strace
captures all the system calls and signals of a process into a text file. It was running for about 15 minutes. Compressed the file is only 22 MB but uncompressed a whopping 1.6 GB, obviously there is a huge amount of repeated text in the file.I have no idea whether this will be helpful in debugging the memory problem. But if there is another program you wish me to use to monitor the process then let me know. If there was a publicly available bug tracker I could upload the file, place a comment, and know that the right devs would see the data - I don't even know if the devs are monitoring this thread, or even if the bug is being worked on as a matter of priority, I hope so.
Being a
strace
newbie I used a basic command (12578
being the Vivaldi process taking the RAM):sudo strace -o vivaldi_ram_problem_strace -p 12578
Here is the link to the data file: vivaldi_ram_problem_strace.zip
OS: GNU/Linux x86_64 Kernel: 3.13.0-24-generic Distro: Linux Mint 17 Qiana, Cinnamon 64-bit 2.2.16 [Based On: Ubuntu 14.04.5 LTS, Trusty Tahr]
Vivaldi 1.14 consumes infinite amount of RAM. Can I download infinite amount of RAM in a finite time?
Only if
P = NP
. Of course if you can prove that you can claim the Millennium Prize of USD $1 million and that'll buy a serious amount of RAM. -
@jkierzkowski Hm, opening a new window is known to trigger the bug, especially when done with Ctrl+N (which can be reliably reproduced by now, so fixes are on the way) - but opening a tab? ...
... that should have hit me multiple times by now because I am a convicted tab hoarder with varying amounts of tabs open in a daily session.
Multiple monitors are part of the culprit too, but not necessarily needed, it only makes it appear faster.