Too much RAM usage, too many processes, very, very slow
-
Hello, Windows 8,1, all updates, x64. Intel N3540 2,16 GHz, 4 GB RAM. - Vivaldi Beta, updated. When I push to start Vivldi (once only, of course) - I wait about 2-3 minutes... and Vivaldi start, but 8-9 Vivaldis, and 20-30 processes :woohoo: (see image). [attachment=1995]Untitled-2.jpg[/attachment] When I close Vivaldi, and I work on 1 window (with 1-2 tabs only), procesesses not close - ane usage of RAM and procesor is very big! Normally I use Firefox with about 100 tabs!... and it's works...
It is bug? What can I do? I want to work with Vivaldi, but it is no good. Cheers, Karol Attachments: [img]https://forum.vivaldi.net/uploads/attachments/70328/Untitled-2.jpg[/img]
-
@op
Close vivaldi go in your user profile and delete current tabs, current session, last tabs and last session.
Surely they are messed up.
-
Typically, Vivaldi (and all chrome-based browsers) will open one process for each tab currently present, as well as one process for each extension, plus a couple of more processes for the browser itself and its graphics system. As a result, with a lot of open tabs in Vivaldi, in Task Manager you will see a lot of running Vivaldi-related processes with their various resource demands. These separate processes, among other things, keep a crash in one tab from crashing the entire browser. When Vivaldi is properly closed, all the various Vivaldi processes should end at more or less the same time.
On the other hand, Firefox uses a single process for everything, so opening up many tabs will greatly increase the resource demands of the single running process. While this architecture is perhaps a bit more resource-efficient, it makes the entire browser sensitive to a crash in any tab.
With either Vivaldi or Firefox, running 100 tabs will cause very heavy resource loading, with Vivaldi showing lots of moderate-sized processes and Firefox showing one very large process.
If you close Vivaldi by normal means, all its related processes should end fairly quickly (within a few seconds). If Vivaldi processes keep on running after Vivaldi has been closed, there is something wrong with the closing operation or something that was running in one or more of the tabs is hanging things up (Flash, etc). If a problem exists in an open tab, that problem may recur if you reopen the browser to the same tab session after closing down the browser. Thus, you should try what @The_Solutor has suggested above in order to remove any problems that are being carried over from a prior session.
-
Thank you, I understand. It works - trouble was in RAM-eaten sites in many tabs (sites offline, which I save on hard disk), I mean. Now - 5 tabs, work normally, start normally.
Cheers,
Karol -
Good! And thanks for reporting back your results… reading them may help somebody else later on, along the way.
-
These separate processes, among other things, keep a crash in one tab from crashing the entire browser.
[…]
[Firefox] architecture is perhaps a bit more resource-efficient, it makes the entire browser sensitive to a crash in any tab.
Yeah, because browsers crash all the time, don't they! :whistle:
I never understood that argument, from the moment Chrome came out and started parading this waste of resources as an "advantage"…
-
… Yeah, because browsers crash all the time, don't they! :whistle:
I never understood that argument, from the moment Chrome came out and started parading this waste of resources as an "advantage"…I've had browsers crash around once every week or ten days, usually in browsing to new sites (and no, they're not 'dodgy' sites). It's happened with Olde Opera, Firefox, and single tabs in Vivaldi and QupZilla. The more tabs open and the more graphics or animation-rich the sites, the more likely it seems to occur. Just sayin'
-
At least 2 of those vivaldi processes are those extensions you're running.The other three is one for your one tab, and one for the user interface. The other I'm not so sure. Probably the graphics processing.
-
@Aikimaniac:
That is all nice but does not change the fact that technically is Vivaldi much slower (i do not criticize since it is beta and i like it a lot) when starting program or page opening (with cleaned cache) when i compare it to Chrome, Opera or FF… lets hope that this will change and it will be very quick browser...
I agree. I'm using Vivaldi as my main browser since TP4 and I feel that is a resource-eater. I use to have about 10 tabs opened and Vivaldi is slower than the others browser opening and surfing over internet.
In my desktop I don't have any problem because is powerful enough but in the laptop… when I have several tabs opened and including some "heavy" pages with images, videos, etc. Vivaldi is quite slow. For instance with the same pages Firefox works flawlessly.My specs are: AMD A-4500M, 8GB Ram and W10x64. I used Vivaldi snapshots of 64 bits and now I made a clean installation of Vivaldi beta 32 bits with no difference in performance.
I know that Vivaldi is in his early stages, with a brand-new beta but I think it should make some improvements in the performace.
-
Hardware has a lot to do with it. On my 3-year-old AMD 6-core 3.5 GHz, 10 GB Ram system, I am literally unable to discern any speed difference between Vivaldi and any other browser at this point. Further, with up to 25 tabs open at once for literally days at a time, it never requires enough resources to max out or slow down the system. That doesn't mean there aren't optimizations to be done. There are TONS that need to be done. It's just that I have enough resources at my disposal that the lags and demands don't impact my senses.
So it's not like the product is a disaster or something. It's just that it's resource hunger needs to be, and will be, improved.
-
Vivaldi sure still is a resource hog, even when compared to other Blink based browsers. I'd love to use it as my main browser, but I still can't - with my average of 50 tabs open, its UI response gets progressively slower and slower over time to the point where I just can't stand it anymore. It's especially noticeable when switching panel on/off, switching video to fullscreen and stuff like that - after a few hours of normal browser usage, things like that can even take several seconds to finish. That's on an i5 system with 16 gigs of RAM, running from an SSD.
And even freshly started, Vivaldi still responds visibly slower than current Opera with the same set of tabs loaded. And, as I've said, it only goes downhill from there as time passes.
I'm really looking forward to future optimizations. They can't come soon enough for me
And I really hope it'll be possible to make the UI more responsive.
-
Ppafflick unlocked this topic on
-
Ppafflick moved this topic from Vivaldi for Windows on