Vivaldi uses all of the available memory after udate to 1.14
-
I disabled all extensions and it seems to be doing the same thing
-
@frozenform How much available memory is there, and are you on 32-bit, or 64 bit? We have a developer particularly interested in this issue at the moment, and this info might be important. I can't reproduce it on X64, but I do run out of memory (3.75 GB only) on X86.
-
I'm using the 64bit version of vivaldi. I have a total of 113 tabs open in 4 windows. The "Browser" task is shown as using the most memory, jumping 4GB and ~100-ish MB.
My PC main specs:
Ryzen 1600x
16GB RAM
Radeon RX 480 4GB -
@frozenform And how much RAM do you have available?
-
@ayespy 16GB
-
@frozenform Thanks. And your OS?
-
@ayespy Windows 10
-
@frozenform Thank you.
-
@frozenform How long do you have to wait for this to happen? Any specific actions?
Also, with leaks like this, it's often useful to enable the Handles and GDI/User Objects columns in Process Explorer. When one of those starts leaking, the count will climb dramatically, and that can deplete main memory (not that I've seen this happen with Vivaldi, but in other cases over the years).
-
@rseiler As suggested I enabled the columns.
The numbers seems consistent between restarts and don't change much while running.
Vivaldi starts consuming about 300MB ram per second after the browser becomes usable, as in when tab content appearss in all windows. -
Can you start it with a dummy profile as a test? You're sort of running out of things that it can be. A rogue plugin (as opposed to extension, that you've accounted for)? Video driver (hard to believe)?
-
@teacup 3GB for 40 tabs in a Chromium browser (especially if you're using the x64 version)? That's normal, maybe even better than average. I'm sitting at 3-5GB all day every day, and I almost never reach 40 tabs. Though maybe you mean more a rapid ascent to that figure, and especially the crash. That's not normal.
-
@teacup Your information has been forwarded to the Team.
-
How could I test with/without plugins? I haven't installed anything extra and the plugin page seems to be removed from chrome.
Some interesting things I found:
If a save the offending session, close everything, and just have an empty window memory usage returns to normal, but if I then reopen a window from the trash button, the memory usage issue returns. But if i shutdown vivaldi with just an empty window and then restore windows one-by-one from the trash button everything works normally, but if I then restart with all windows open the memory issue returns.If I put all my windows in a single monitor, there is no memory issue on startup, but it return once i open a new tab.
Dragging a window to a different monitor seems to increase memory usage by about (2~4)x(tab count) MB (or something close)
My primary monitor is 1920x1200, index 2; my secondary monitor is 1440x900, index 1
-
Using the instructions in the last post, I wasn't able to replicate the leak (I'll try again though), but I did replicate the ~80% CPU issue reported here! The second window is what does it.
-
Quad-core. Here's a shot of the before/after.
Yes, it wouldn't surprise me at all if this was part of the same issue. I can't happen to trigger the memory leak (I may not be waiting long enough), but the CPU problem is easy. You can do the reverse. Some may be able to do both.
-
Not sure about the memory leak part, but the CPU explosion part still happens in the first 1.15 beta.
-
@frozenform Any difference with the first maintenance release of 1.14?
-
@teacup
@rseilerI am able to reproduce the 100% CPU usage (all 4 cores) and severe memory leak using the two monitor, two window approach.
I am not able to reproduce on single monitor.I'm using Windows 10, Vivaldi 64-bit. The crash occurs when all RAM, 16 GB, is used.
The CPU utilization and memory leak stops when the new tab AND new window is closed.
-
@gwen-dragon
I have no extensions installed.
I don't know how relevant this is but some more information: I'm consistently reproducing the issue with 12 open tabs, one of them fully loaded, in the main window, the second window has just one tab with speed dial, the 100% CPU and memory leak fires in most cases with second or third new tab (only with speed dial) opened. Less often it fires on the first new tab, even less often it fires later (10, 15, ... new tabs).Looking at the Vivaldi Task Manager, the CPU usage is split between 'Browser' and 'Background Page', Memory footprint increases for 'Browser'.
So far, I wasn't able to reproduce the issue if the second opened window is private.