Vivaldi 2.2.1373.4 bombs on *every* Quit
mettarefuge last edited by xyzzy
When I quit, via menu or command-Q, Vivaldi bombs with this error, which is sent to Apple (not whole message) below:
Process: Vivaldi 
Version: 2.2.1373.4 (2.2.1373.4)
Code Type: X86-64 (Native)
Parent Process: ??? 
Responsible: Vivaldi 
User ID: 502
Date/Time: 2018-11-27 00:18:51.253 -0800
OS Version: Mac OS X 10.14.1 (18B75)
Report Version: 12
Anonymous UUID: CF470908-206D-8E1C-9F86-3B2AAB069D80
Time Awake Since Boot: 21000 seconds
System Integrity Protection: enabled
Crashed Thread: 0 CrBrowserMain Dispatch queue: com.apple.main-thread
Exception Type: EXC_BAD_ACCESS (SIGSEGV)
Exception Codes: EXC_I386_GPFLT
@mettarefuge When you Quit, lots of things need to happen in order for Vivaldi to shut itself down in an orderly manner and (if applicable) to allow you to resume the last session when you restart... and something somewhere in the middle of that process is triggering a crash.
Do you have any extensions installed and if so, could you please disable them all and then try re-enabling them one-by-one until you find the one that's triggering your crash?
If the crash not extension-related, please file a bug report. When you get the confirmation email from the bug tracker, please also reply to that email and attach a copy of the complete crash log.
Thanks for some guidance. Yes, I have and use extensions -- 40 of them -- the exact same 40 I have in Chrome, which doesn't bomb when I quit. This kind of trouble-shooting is so time consuming. When I have some "free" time, I'll look into this. In the meantime, it's back to Chrome. And yes, I've already submitted a bug report using the Console's log information. Thanks for taking the time to respond.
@mettarefuge Thanks. I see your bug report but I don't see any crash logs attached. Could you please create an unformatted text file with TextEdit.app, paste a copy of the entire crash log, and send it as an attachment via reply email to your bug confirmation? Without that additional information, the bug will get closed. In order to fix the crash, the developers will need to know specifically where in the code that the crash occurred, and will also likely need to be able to reproduce the crash in their development/debug environment.
Please also note that not all Chrome extensions are compatible with Vivaldi. In fact, many can't work because the Vivaldi developers have either removed, disabled or replaced code that interacts with Google's back-end systems.
Thanks! Will send the works as an attachment to the bug e-mail. (I assume you mean the e-mail I got and not the partial crash report I used, above, here at the forum.)
Happily, the vast majority of extensions work with both Vivaldi (and Opera, though Opera does make some Opera-specific extensions)...the only ones that haven't worked seem to be ones that tie into the Google ecosystem, like those for Google Keep and the like.
Thanks for your attention here. Much appreciated.
Knuthf last edited by
@xyzzy You have a problem with "focus" - or MacOS has a problem. Vivaldi sets something that takes resource: You cannot move Vivaldi between workspaces.
I suspect High Sierra / 10.13.6 to have a bug because you got a "kernel panic" where I had to restore, could not just reboot. I blamed this on Apple and the release of MacOS. They have made changes but I don´t know what happened.
But just in case: Reboot with "Cmnd+R" and select "Disk Utility" - here do "Repair" on the main disk, which erases temporary items. Then you can start up. Otherwise your Mac can hang with grey screen. The option is made to allow you to fix errors in the file system and get the Mac going still.
Re: your kernel panic... Nothing in Vivaldi should cause macOS to panic, at least not directly, because Vivaldi does not install any low-level code that could crash the operating system. However, it can potentially trigger a panic due to buggy low-level 3rd-party code. For example, if you have a non-Apple USB device installed that requires a custom device driver that installs as a kernel extension, and if that driver has bugs, then that's a kernel panic waiting to happen. Chromium's WebUSB code periodically enumerates USB devices, and that can then trigger a panic or can cause the browser and/or a user-mode USB device driver to crash. Chromium's GPU hardware acceleration can also potentially trigger a crash in a buggy graphics driver, especially if you enable experimental graphics-related flags.
mettarefuge last edited by mettarefuge
Thanks for your tips. I haven't done the command-R thing in a while. Maybe that will help, and not just Vivaldi! (I have not been having any kernal panics or system bombs of any sort, btw.) The only thing bombing is Vivaldi...it fails and I get the "send a report to Apple dialog, which I do.) My machine is otherwise unaffected.
Anyway, much appreciated. Steve
This tech stuff is beyond my pay grade, but let me note that the only thing "bombing" is Vivaldi—the system and other programs I'm running are unaffected. Vivaldi bombs and I get the "report this to Apple dialog" and I always do.
Also, since I'm not getting bombs with Chrome or Opera, I wonder how likely it is that its Chromium WebUSB code. I am not aware of any of my USB devices "crashing" including several har drives and my mouse and keyboard.
For fun, I just turned off hard-ware acceleration in Vivaldi to see if that might affect things.
Anyway, to be clear, it's *Vivaldi" that's bombing out when I quit it...nothing else seems to be affected. Thanks much, and all, Steve
mettarefuge last edited by xyzzy
Turned off hardware acceleration and Vivaldi still bombs when I quit...I just sent this report to Apple...(this is only the first part, not the whole report)
Process: Vivaldi  Path: /Applications/Vivaldi.app/Contents/MacOS/Vivaldi Identifier: com.vivaldi.Vivaldi Version: 2.2.1373.4 (2.2.1373.4) Code Type: X86-64 (Native) Parent Process: ???  Responsible: Vivaldi  User ID: 502 Date/Time: 2018-11-28 19:47:27.709 -0800 OS Version: Mac OS X 10.14.1 (18B75) Report Version: 12 Anonymous UUID: CF470908-206D-8E1C-9F86-3B2AAB069D80 Time Awake Since Boot: 17000 seconds System Integrity Protection: enabled Crashed Thread: 0 CrBrowserMain Dispatch queue: com.apple.main-thread Exception Type: EXC_BAD_ACCESS (SIGSEGV) Exception Codes: EXC_I386_GPFLT Thread 0 Crashed:: CrBrowserMain Dispatch queue: com.apple.main-thread 0 com.vivaldi.Vivaldi.framework 0x00000001132deb54 0x10e00e000 + 86838100 1 com.vivaldi.Vivaldi.framework 0x000000010f356f45 0x10e00e000 + 20221765 2 com.vivaldi.Vivaldi.framework 0x000000010f358c7d 0x10e00e000 + 20229245 3 com.vivaldi.Vivaldi.framework 0x000000010f3588b3 0x10e00e000 + 20228275 4 com.vivaldi.Vivaldi.framework 0x000000010f373b46 0x10e00e000 + 20339526 5 com.vivaldi.Vivaldi.framework 0x000000010f373aa1 0x10e00e000 + 20339361 6 com.vivaldi.Vivaldi.framework 0x0000000112b72369 0x10e00e000 + 79053673 7 com.vivaldi.Vivaldi.framework 0x000000010f15f513 0x10e00e000 + 18158867 8 com.vivaldi.Vivaldi.framework 0x000000010ee9e24c 0x10e00e000 + 15270476 9 com.vivaldi.Vivaldi.framework 0x0000000110fc49db 0x10e00e000 + 50031067 10 com.vivaldi.Vivaldi.framework 0x00000001108e47ed 0x10e00e000 + 42821613 11 com.vivaldi.Vivaldi.framework 0x00000001108ffc1f 0x10e00e000 + 42933279 12 com.vivaldi.Vivaldi.framework 0x00000001108fff73 0x10e00e000 + 42934131 13 com.vivaldi.Vivaldi.framework 0x00000001109b2bba 0x10e00e000 + 43666362 14 com.vivaldi.Vivaldi.framework 0x00000001109b637a 0x10e00e000 + 43680634 15 com.vivaldi.Vivaldi.framework 0x00000001109b251f 0x10e00e000 + 43664671 16 com.apple.CoreFoundation 0x00007fff48961155 __CFRUNLOOP_IS_CALLING_OUT_TO_A_SOURCE0_PERFORM_FUNCTION__ + 17 17 com.apple.CoreFoundation 0x00007fff489610fb __CFRunLoopDoSource0 + 108 18 com.apple.CoreFoundation 0x00007fff48944b95 __CFRunLoopDoSources0 + 195 19 com.apple.CoreFoundation 0x00007fff4894413e __CFRunLoopRun + 1219 20 com.apple.CoreFoundation 0x00007fff48943a28 CFRunLoopRunSpecific + 463 21 com.apple.HIToolbox 0x00007fff47bdcb35 RunCurrentEventLoopInMode + 293 22 com.apple.HIToolbox 0x00007fff47bdc86b ReceiveNextEventCommon + 618 23 com.apple.HIToolbox 0x00007fff47bdc5e8 _BlockUntilNextEventMatchingListInModeWithFilter + 64 24 com.apple.AppKit 0x00007fff45e98eb7 _DPSNextEvent + 997 25 com.apple.AppKit 0x00007fff45e97c56 -[NSApplication(NSEvent) _nextEventMatchingEventMask:untilDate:inMode:dequeue:] + 1362 26 com.vivaldi.Vivaldi.framework 0x00000001108bc960 0x10e00e000 + 42658144 27 com.vivaldi.Vivaldi.framework 0x00000001109b637a 0x10e00e000 + 43680634 28 com.vivaldi.Vivaldi.framework 0x00000001108bc894 0x10e00e000 + 42657940 29 com.apple.AppKit 0x00007fff45e91cb9 -[NSApplication run] + 699 30 com.vivaldi.Vivaldi.framework 0x00000001109b347c 0x10e00e000 + 43668604 31 com.vivaldi.Vivaldi.framework 0x00000001109b1ffe 0x10e00e000 + 43663358 32 com.vivaldi.Vivaldi.framework 0x000000011091efd5 0x10e00e000 + 43061205 33 com.vivaldi.Vivaldi.framework 0x00000001104cc1bd 0x10e00e000 + 38527421 34 com.vivaldi.Vivaldi.framework 0x000000010ed2a764 0x10e00e000 + 13748068 35 com.vivaldi.Vivaldi.framework 0x000000010ed2ca82 0x10e00e000 + 13757058 36 com.vivaldi.Vivaldi.framework 0x000000010ed270e1 0x10e00e000 + 13734113 37 com.vivaldi.Vivaldi.framework 0x000000011049030b 0x10e00e000 + 38281995 38 com.vivaldi.Vivaldi.framework 0x00000001121072dd 0x10e00e000 + 68129501 39 com.vivaldi.Vivaldi.framework 0x000000011048f4f4 0x10e00e000 + 38278388 40 com.vivaldi.Vivaldi.framework 0x000000010e01265f ChromeMain + 175 41 com.vivaldi.Vivaldi 0x000000010bdabdde main + 382 42 libdyld.dylib 0x00007fff75b2108d start + 1
Your crash actually looks familiar... similar to a crash that I also reported. If it's what I think it is, it's not directly extension-related and disabling hardware acceleration won't have any effect... and the devs are working on a fix.
Ah, thanks, my friend, for the clarification...perversely, it's always "comforting" to hear someone else has a similar bug, instead of something being soley some idiosyncrasy of one's own system! Glad to hear the software ninjas are at work on a fix of this possible bug.
Thanks again, Steve
Don't know if it's relevant, but Vivaldi also ignores command-Q...and it's still bombing every time I quit. I've send dozens of bomb reports to Apple via their app bomb dialog box...
@mettarefuge Chrome 71 is due to be released in a few days and the Vivaldi devs are working hard to get Vivaldi 2.2 (that's based on Chromium 71) stable enough for release. I'm still a bit surprised that you're getting a crash on every Quit. That's not normal. For me, crashes are few and far between.
I also don't know if sending the crash reports to Apple will help... or how the devs deal with crash reports that get passed on to them from Apple of the blue... of if they even receive those crash reports.
FYI, if you should ever need to review or compare previous crash reports, you can launch Console.app (it's in the "Other" folder in Launchpad) and go to the "User Diagnostic Reports" section. There's no need to send them all to Apple or to the Vivaldi team unless the crash signature changes.
Thank for further help and input—and insight into how to further troubleshoot.
Maybe the Chromium 71 version will "magically" fix this irritating bug.
I have thought of doing a total "nuke" of Vivaldi, using a program I have called AppDelete, and searching out the least crumbs with my Path Finder program. With a fresh install of Vivaldi, it's not hard to import most of what I need from Chrome, but I am loathe to have to find and re-install all my extentions.
Any thought on this?
Thanks for your persisent and skillful help.
@mettarefuge Hopefully, a new 2.2 Snapshot build should be out soon. Let us know if that fixes the problem.
FYI, help.vivaldi.com has instructions on how to perform a Full Reset of Vivaldi, should you choose to go that route, and one of my fellow Moderators has posted tips on how to refresh your Vivaldi profile should the browser ever suddenly start acting strangely.
Thank you, and will let you know here.
And thanks for those links on a reset. When I have a moment, I’ll look into them. Much appreciated.
Vivaldi 2.2.1387.4 (Official Build) (64-bit)
Huzzah! Just downloaded the new update, and no "crash on quit" and command-Q works again!
There are some neat new features in this, too...esp. love the save tabs as session feature.
Thanks again for all the thoughtful input and help.
With best wishes,
@mettarefuge Thanks very much for the update, for your help in troubleshooting this issue and for your bug report, which I will now close. I'm glad to hear that the latest Snapshot is working well for you!