Vivaldi cannot be quitted.
-
@xyzzy OK I have to ask, are both those installs you are using on the same system? If they are, how do you run two different versions of Vivaldi on the same system?
That would be of interest to me.
@ryofurue I too have had problems with the shutdown, where neither function has worked. I was forced to do "forced quit" and then the trouble with doing that, is I seem to lose random bits of cookie information, that normally help me. The only reason I can logically figure out for the loss of that info, compared to when I did not have to force it to quit, is actually doing too many forced quitting events.
There is a difference for me though, I am a super heavy user with more tabs and windows opened and hibernated than even most heavy users probably have on average. I did a refresh on the browser, and the problem seemed to still be there, but more intermittently, and the following problems mentioned as a result, seem to remain, even before I began reinstalling extensions I actually used and needed, and any other data I wanted to keep.
Since then, I've been left with many questions about where and how certain bits of data that makes the browser run and remember the right information is actually stored.
Even with a complete refresh, by changing the name of the default folder, it only took like two files to bring back a lot more data than what the files names suggested should be stored in them. It was weird, what was lost, fixed, and then the process of rebuilding. I thought I would need more files replaced to get the data that is suggested we keep, but that was not the case.
-
@justintaylor I'm actually still running El Capitan. As far as I can tell, (all?) Mac users running into this problem are running Vivaldi 1.16 Snapshot builds on High Sierra.
I also don't normally have many tabs open and in my "daily use" Vivaldi installation and I start up with the Start Page; I don't resume my last session.
We're still not sure if this is triggered by internal changes within the Chromium 67 browser engine, extensions, the number of tabs open, internal changes to the Vivaldi code required to support Chromium 67, or a combination of factors.
This issue has everybody's attention internally right now.
-
@xyzzy said in Vivaldi cannot be quitted.:
@ryofurue The only thing that I can think of is that either something has become messed up in your Vivaldi profile or that you have a problematic extension installed. Are you able to Quit if you disable all of your extensions?
I'm afraid not. I removed all extensions and restarted Vivaldi. Still I'm not able to quit Vivaldi.
Eventually I'll erase my profile and start over. The problem may go away.
-
@ryofurue I'm still wondering what could be running inside Vivaldi that won't allow it quit. While this problem is still going on, could you please do the following?
- Before Quitting Vivaldi, open Vivaldi's Task Manager and take a screenshot of all the running Tasks.
- Open the macOS Activity Monitor to view all of the running processes in macOS
- Quit Vivaldi
- Go back to Activity Monitor and note the Process ID (PID) of any Vivaldi processes left running. (If you prefer using the command line,
ps -ef | grep -i vivaldialso works; the PID is the number in the 2nd column.) - Go back to the Task Manager screen shot and locate the lingering Tasks from their Process ID.
We can do more in-depth troubleshooting later but hopefully this will provide some insight as to what tasks are not exiting cleanly.
Thanks!
Soprano / Moderator (and volunteer -- I do not work for Vivaldi) • Report a Bug • Community Code of Conduct
-
@xyzzy Hi, do that procedure apply to Linux as well?
-
@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.
Soprano / Moderator (and volunteer -- I do not work for Vivaldi) • Report a Bug • Community Code of Conduct
-
@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
-
@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.
-
From Man Pages
ps displays information about a selection of the active processes. If you want a repetitive update of the selection and the displayedThere 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 -
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.
-
@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!
-
@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).
-
@nssynapse Wow, very interesting. Thanks!
-
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!
-
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.
-
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 -
@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.
-
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 -
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 -
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
