Infinite RAM usage
-
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.
It all started after I upgraded Vivaldi to 1.14 yesterday.
Linux Mint 17.3, 64 bit.I've just reported a bug about it, but I also wanted to ask here if anyone has the same.
-
@jkierzkowski Nope.
I'm about to go to bed, meaning that V-SS has been running continuously ~14.5 hrs:
-
@gwen-dragon
Here's a screenshot I've just taken.
You can see all the extensions I have enabled.
None of them was recently updated (only Tampermonkey was updated, but I turned it off to check if it is the reason – it's not, as we can see).
I have quite many tabs opened, some of them pinned, but (almost) all hibernated.
No GMail tab, only the GMail extension.
Some YT tabs, but hibernated, as mentioned.Now I see, that it happens when I open a new tab other than those opened on Vivaldi start.
Is there any debug-mode run from a command line? Or can I do anything else?
-
Now I see, that it happens when I open a new tab other than those opened on Vivaldi start.
I opened a new Vivaldi window and closed both old windows.
I can open as many new tabs as I want and RAM is OK, but the CPU is highly loaded. And the GPU process looks strange.Linux console shows this, when I run Vivaldi from there (don't know if it's important):
[26135:26135:0202/142402.991031:ERROR:gles2_cmd_decoder.cc(18162)] [.DisplayCompositor-0x1c072210e00]GL ERROR :GL_INVALID_OPERATION : glCreateAndConsumeTextureCHROMIUM: invalid mailbox name
[26135:26135:0202/142402.991334:ERROR:gles2_cmd_decoder.cc(10008)] [.DisplayCompositor-0x1c072210e00]RENDER WARNING: texture bound to texture unit 0 is not renderable. It maybe non-power-of-2 and have incompatible texture filtering. -
I installed Vivaldi v.
1.14.1077.41 (Stable channel) (64-bit)
yesterday. After several hours, with 4 or 5 windows open and 100+ tabs (best guess), my desktop stopped responding properly, even my mouse pointer and clicks became heavily delayed. On investigation I discovered that Vivaldi was using 14.2 GB of memory (my system has 16 GB RAM) andps
listed several dozen Vivaldi processes. At this point my system was responding so slowly that I was forced to kill the processes withkillall -9 vivaldi
.Please note that I never experienced a memory problem with Vivaldi v.
1.13.1008.36
.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]
-
I confirm. After few hours of browsing, with only one tab (Vivaldi forum) opened now, the process "Browser" consumes 1 GB of RAM.
-
@viava said in Infinite RAM usage:
I confirm. After few hours of browsing, with only one tab (Vivaldi forum) opened now, the process "Browser" consumes 1 GB of RAM.
That sounds fairly normal to me...
I encountered the issue the others are referring to when I was using the 1.14 Snapshots/RCs. For me it usually involved a lot of seemingly unnecessary CPU use as Vivaldi progressively consumed more and more RAM & SWAP fairly quickly until things started becoming unresponsive and Vivaldi eventually needed forcibly killed. -
@hekel
I do not find this as normal. IMHO, it is a bug.
When Vivaldi starts, the process "Browser" consumes ca 100 MB (with one tab opened). So Vivaldi should release unused memory during normal browsing and after closing of all unused tabs (with one open tab only left) a RAM consumption of this process should return to the initial 100 MB. -
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.