Vivaldi cannot be quitted.

[lamarca]

@xyzzy Hi, do that procedure apply to Linux as well?

[xyzzy]

@lamarca The general approach applies to troubleshooting this issue on any operating system, including Linux and Windows. Vivaldi is not shutting down so we need to see what Vivaldi processes are still running at the operating system level, and then use the Process IDs to match them to the problematic Vivaldi tasks that are still running.

It's entirely possible that this may not provide much insight into what's actually broken but it does give us a starting point on where we need to focus our troubleshooting efforts.

[lamarca]

@xyzzy Although my Mac knowledge is close to zero, I know about the Terminal, sudo. The "ps" command line got my attention. grep using the switch -i to ignore case sensitive words. The start time might help. My Vivaldi uptime is 01:26:38
CLI addicted.
Thanks for the reply.

Cheers

[xyzzy]

@lamarca ps is just the standard UNIX command for displaying the status of running processes. If your Linux distro does not like the UNIX-style options, you can also try ps ux | grep -i vivaldi (Note that there is no "-" with this variant; this works on macOS as well.)

Microsoft Windows users can use the OS's Task Manager (or tasklist from the command line, or utilities such as Process Explorer) to display running processes and their Process ID's.

[lamarca]

From Man Pages

ps displays information about a selection of the active processes.  If  you want a repetitive update of the selection and the displayed

There are many alias to exec 'ps', which has different functions, also, ps is present in the Bind builtin featute.

Ever tried this? curl -s httpbin.org/ip | jq -r .origin

[mettarefuge]

@tbgbe

Yes, same problem here...MacOS 10.13.6 and Vivaldi 1.16.1246.7 (Official Build) (64-bit).

Have to force quit every time. Doesn't matter if all extensions are turned off, btw. It just ignores the Quit command, whether command-q or from menu.

[xyzzy]

@mettarefuge (and to anybody else running into this issue) If you Quit Vivaldi and it does not exit, before you Force Quit, could you please open Activity Monitor on macOS and count the number of Vivaldi process that are still running? Are there only a few Vivaldi processes remaining or a whole bunch of them? What we're trying to figure out is whether a single task is holding up the browser shutdown or if some other glitch is occurring early in the shutdown procedure and preventing everything else from shutting down cleanly. Thanks!

[NSSynapse]

@xyzzy, I just did the test you suggested (Vivaldi v1.16.1246.7 had been running for 3 hours at that point):

Vivaldi processes in Activity Monitor before invoking "File->Quit Vivaldi": 29
Vivaldi processes in Activity Monitor after invoking "File->Quit Vivaldi": 29
(Vivaldi's own Task Manager only shows 18 of those processes, both before and after invoking quit)

In other words, not only is there no visible response to invoking quit, none of the processes get terminated either.

I read on Slack that you suggested that the issue might be with the internal lock hierarchy and something not getting released when it should. Here is an observation that might lend support to that hypothesis:

Yesterday, I invoked quit but then instead of force-quitting Vivaldi, I just kept using it. After an hour or two, Vivaldi did all of a sudden quit (definitely a quit, not a crash), right after I closed a tab. As if closing that tab "unlocked" Vivaldi so that it could finally initiate the shutdown.

Before the Chr67 intake, it would happen to me occasionally that Vivaldi would not quit after I invoked quit, but back then, I could always get it to quit by opening a new tab with ⌘T and then closing it with ⌘W. Since the Chr67 intake, this workaround no longer works and quit seems to reliably stop working after a very short amount of time, whereas before, quit would only once in a while stall (until I opened a new tab and then closed it).

[xyzzy]

@nssynapse Wow, very interesting. Thanks!

[xyzzy]

Just to keep everybody up to date, we've actually done quite a bit of brainstorming internally as to what could be causing the shutdown issues.

For those affected, the problem seems to occur when people have multiple tabs open and after Vivaldi has been running for some time. For those that resume their last session, when they launch Vivaldi and then immediately Quit, the browser (usually) shuts down cleanly. So, this likely has something to do with hibernated/inactive tabs impeding the browser shutdown in some way.

If any of you have any other information, workarounds or insights that you can share, we'd really appreciate it.

Thanks!

[xyzzy]

Okay... I just found a way to replicate this consistently with a new default Vivaldi install:

• Launch Vivaldi (Vivaldi opens with the Start Page)
• Open 30 tabs (from bookmarks in background tabs)
• Wait for the pages to load, then Quit. (That works.)
• Launch Vivaldi again (resumes previous session)
• Open another 30 tabs (from bookmarks in background tabs)
• Wait for the pages to load, then Quit.

This time, nothing happens. Something is stopping the browser from shutting itself down.

If I go back to the Start Page tab and "close other tabs", the browser gets "unstuck" and is then able to complete the shutdown.

[mettarefuge]

@xyzzy

I still can't get Vivaldi to quit. I ran the activity monitor, as requested, and I found 36 processes running.

Looks like this:

1.16.1259.3 (Official Build) (64-bit)
Revision 9692f1b5efe9718f1ededb9a89f025be92848312-refs/branch-heads/3440@{#132}
OS Mac OS X

[xyzzy]

@mettarefuge Thanks for the update. After finding a way to reproduce this, I've also done some more troubleshooting of my own. After I Quit Vivaldi, I tried closing tabs, one by one... and Vivaldi eventually shuts down. Digging deeper, it looks like some resources of closed "hibernated" tabs are still being held internally until a specific active tab gets closed. (I have no idea why.) So, something is causing Vivaldi to get "stuck" and not allowing it to shut down cleanly.

It also only seems to happen if you have more than a certain number of tabs open (40? ...not totally sure) so depending on how you use Vivaldi, you may never run into this glitch.

[mettarefuge]

@xyzzy

Even if the problem remains mysterious, it's always comforting to have someone else reproduce your problem, so you know it's not some individual glitch that can't be fixed because it's just your own unique set up, computer, etc. etc.

Intuitively, the issue does seem to have to do with having a LOT of tabs open...I typically have at least 30 or more and often double that. I hope that the code ninjas will take this hint and see why some of us can't quit Vivaldi. For all its wonderful features, not being able to Quit is the very least one should expect from a browser.

Frankly, I find it so annoying, having to Force Quit to Quit, I've stopped using Vivaldi until some update (one hopes) fixes it...

Hope the bug can be found soon. I DO love the features of Vivaldi.

Best wishes,
Steve

[mettarefuge]

@xyzzy

After I posted, just a few minutes ago, I thought about your comment: " Digging deeper, it looks like some resources of closed "hibernated" tabs are still being held internally until a specific active tab gets closed. (I have no idea why.) So, something is causing Vivaldi to get "stuck" and not allowing it to shut down cleanly."

THAT reminded me of a problem I had quite some time ago with an Extension that was apparently constantly talking to a databse server...it's a "support" extension for the (great, in my opinion) FVD Speed Dial. Anyway, I just tried disabling the EverSync extension, and voila! Vivaldi QUITS with no problem! Even with 80 tabs open.

Here's the link to the apparent culprit in the Chrome Web store:

https://chrome.google.com/webstore/detail/eversync-sync-bookmarks-b/iohcojnlgnfbmjfjfkbhahhmppcggdog

The thing is, unless I want or need to sync, I can turn OFF the Eversync extension and still use the FVD Speed Dial extension that Eversync supports.

I don't know if others who can't quit are using this particular extension, but maybe it's a clue, and maybe this clue can also help Vivaldi quit, at some point, with the extension enabled, as I can with Eversync enabld in Chrome and Opera and Firefox.

Best wishes,
Steve

[mettarefuge]

@mettarefuge

Ah, crap. Spoke too soon! Disabling Everysync DOES allow me to QUIT, every time, BUT as soon as I get 30 open tabs, I can't quite again!

ARGH!

Well, I hope some of this reporting helps...the disabling of Eversync did "fix" the problem with repeated tests...but with less than 30 plus tabs...

I then tried turning off ALL tabs, and loading 80 tabs, and sonofagun, Vivaldi quits fine every time...so, it's apparently not just Eversync, but some other extension tying things up as well...sigh...I now know why browser developers usually hate extensions...hope some of this helps...I don't have a lot of time to do such stuff, but wanted to help...

Best wishes, again,

Steve

[Ayespy]

@mettarefuge the +- 30 tabs limit is a known issue. Work is ongoing.

[mettarefuge]

@ayespy

Ah, great, that's good news. I understand that a browser can "hang," but Vivaldi isn't hung in these cases...it just wont' quit...any browser should have "God" powers when it comes to shutting itself down the user's direction...

Good luck bug hunting!

[xyzzy]

@mettarefuge This is actually a multi-platform issue; Vivaldi is getting "stuck" and is not able to close down cleanly in some situations. After you Quit... and it looks like nothing happens... if you close tabs, one by one, Vivaldi will eventually be able to close down without having to Force Quit.

I've been able to trigger this reliably with a new/clean/default Vivaldi installation, no extensions. This bug is getting a lot of attention internally and as @Ayespy mentioned, work is ongoing.

[mettarefuge]

@xyzzy

Awesome! I hope a fix comes soon, and thanks to all involved for all the hard work and for creating such a superb, unique, powerful browser!