4G of ram is not enough.
I've been a user since v1, old Opera fan here. This is my first post. I've been planning my exit strategy from Mozilla for a couple of years now, and I WANT to use Vivaldi. I am 100% on board with what you are doing. I've even accepted the fact that this is a Chrome base. (God I dislike Google.)
But...Vivaldi is soaking up so much memory on my dell W7 x64 laptop, solid-state drive, I7 quad core running around 3g (not new, not overclocked,) that if I try to run T-Bird or Seamonkey or eMClient or practically any other large program (or 3-4 smaller ones) alongside Vivaldi I get low-memory errors and crash.
Using process hacker I've seen V using up to almost 2G ram. I usually have 60-100 tabs laying around in a session, and I use --single-process. My only solution is to hibernate backround tabs regularly. Even then it's usually 1.3-1.6G of private bytes.
I am not running Photoshop or Adobe or compiling or processing video with Handbrake. All I really do is ride my email, use the interwebs, write stuff with NotePad++, read pdf's with Sumatra, and keep Keypass alive. Modest requirements in my opinion.
So what do I do from here? I'm running V in portable mode. I'm doing business on this computer and really can't abide these crashes. I appreciate any help the community can offer. Suggestions?
Sorry, I meant "--process-per-site."
Upgrade your RAM if your laptop allows it. RAM is really cheap, if you have the cash and the possibility to do so on your machine, this is certainly a valid option. Going from 4GB to 8GB should do the trick. I'm only running with 8GB myself.
How does it perform when you're using firefox?
What do you have auto-starting?
Adequate swap file?
You could quick try a usb stick or sd card as turbo boost to see if there's a difference.
60-100 is a lot of tabs.
Use V's own task manager (shift-esc) to find any high-ram processes, either tabs or extensions
I hardly ever use a laptop - kind of hate them, truth told.
But when I do use my old Lenovo Core2 Duo, maxed out at 4GB RAM, Vivaldi can max it out with nothing else but a light word processor running. It never crashes, but I get "running out of free memory" warnings. My usual solution is to close some tabs, close Vivaldi, and start anew. Then I'm good for another few hours. It's a PIA, but for now I live with it when I HAVE TO use the laptop. Curiously, I have an older tower that is ALSO maxed out at 4GB RAM, and it never runs out of memory, no matter what (better swapping, mebbe? I dunno). I carted it 600 miles to our new place we are slowly transferring to, just to have something to run there that doesn't make me crazy.
I've resigned myself to the fact that I'm going to have to get another laptop - one less than a decade old.
Old Opera user here.
Very much sympathise; O was amazing even 17 years ago at running 50-100 tabs on a <1GB machine. With V and 8GB I start to get problems over 30-40 tabs.
100 tabs is quite a lot, 50 is moderate and Opera demonstrated that it is entirely feasible.
Hopefully V will get there though!
Old Opera user here.
Very much sympathise; O was amazing even 17 years ago at running 50-100 tabs on a <1GB machine. With V and 8GB I start to get problems over 30-40 tabs. ...
To be fair, though, there's a big difference between running 50-100 typical tabs of 17-year-old vintage compared with 50-100 typical tabs of modern vintage. The vast increase in site-code complexity, remote URL calls, graphics, audio, and all manner of script-driven gee-gaws in a 'typical' tab over those intervening 17 years has been "significant", to put it mildly. The only fair comparison would be what Olde Opera does with the same 50-100 tabs as a modern browser (including consideration of things that might not even work with Olde Opera).
The difference is ye olde Opera didn't run each tab as a separate process. You can't compare it to Chromium.