Since the "memory saver" update, every now and then (honestly pretty often) restoring hibernated tabs just goes into an endless loop where Vivaldi consumes one full core 100% and never ever stops, the tab of course does not load. Closing the tab usually stops the cpu usage (but then reopening it does not always load it properly..). Also what I've noticed is that often tabs from the same site crash in various ways when that happens (so likely something related to one process/site thing + restoring from hibernation).
I don't use memory saver, but I do use lazy load on start.

Am I really the only one encountering this? I'm talking about STABLE Vivaldi on Win (however this happens in snapshots too, I have both Vivaldis on this desktop and both have that issue).

I'm not really willing to clear my profile over and over again, because frankly a lot of updates break things (I still can't use the Vivaldi button menu, because it just isn't there, and the option centers my tabs in the tabbar in some weird way; this was introduced in "revamped menus" STABLE update and never fixed) and for a browser that boasts high customizability (true) not even being able to transfer settings (no, sync wont do that) is a, uh. Plus, it's not just settings but also site data that I'd lose.

With this Snapshot, pressing modifier keys (shift, command, alt) + any key while Dev Tools is open & focused causes the browser to close. Tested & verified on three separate MacBooks (Apple M1 MacBook Pro, Sonoma 14.5).

For instance, trying to type

$

(to access the last selected element) into the Dev Tools console will close the browser.

Aside: I’ve been trying to report this for the last two weeks, but haven’t been able to log in to vivaldi.net due to server errors, though the login screen doesn’t display any error message when submitting the form; I had to inspect network panel to see 400 errors. Today, I wasn’t able to access the login form at all due to a server 500 error. I was finally able to log in today from my iPhone on Safari using the same credentials.

@barbudo2005 I've actually tried to find a CSS workaround for it, but every time I open devtools for window.html the extension icon hides 😁

@luetage BUMP

Hello all.

Not long ago Vivaldi started segfaulting on me. I tried one or two things, but they didn't work. In the end I deleted my config dir, and Vivaldi came back working again.

I've updated a few times since then, I'm using 6.8.3381.48 on Debian Bookworm right now. Yesterday I rebooted my machine to windows, and back to linux, and now vivaldi won't start again, segfaulting.

I could delete my config dir again, but I really really want to try and resolve this as it is a royal pain to have to reconfigure everything again, and again.

I've tried running vivaldi with --dissable-extensions but it still segfaults... I found somewhere in the forums someone mentioning running with --disable-features=Vulkan and I tried it, not that I know/suspect it's my issue, but I'm throwing stuff at the walls... same thing.

I've run vivaldi via gdb but of course the stack trace is not much help without debug symbols. And the stack throws a single line, with an unidentified call.

I've run vivaldi with --no-sandbox (I tried logging, and the last line of the log made me think about trying this, I'll link the log later in this post). Still the same.

I logged out of my desktop (plasma) and logged into gnome, and vivaldi starts.... and asks me to select profile (it wasn't configured so), because it can't decrypt anything, as the wallet changed from kwallet to gnome key ring.... anyhow, I activated "always show this" on the profile select dialog. And closed it so it wouldn't reset my config because it can't read the wallet.... anyhow every time I start vivaldi on gnome it has "show this" active on the profile selector dialog, and still when I run on plasma, segfault, which makes me believe it happens before the load of my profile and all.

I also tried deleting the contents of GPUCache in Default and all profiles to no avail.

Here's my --enable-logging --v=1 output to chrome_debug.log, I see nothing there that suggests a solution but in any case: https://pastebin.com/EAgRxT9h

Is there anything y'all can suggest I try to solve this? I really don't want to have to lose all my config again (except for the few things I can restore from Vivaldi Sync).

(p.s. I run Plasma in X11 since with my nvidia it's slow and unstable in wayland)

@dude99 Brute force upvote! Where do I do this? Have you made a feature request?

@Kjala

Said:

Give Vivaldi that MacOS look.

Could it be that you have a dual personality? 😁 😁 😁