Hi, after the latest vivaldi-snapshot update, it opens up as usual, but if I click on anything, it promptly shuts down. It’s a bit to late to investigate here right now, but is anyone else experiencing this too?
I obviously have other browsers so it’s nothing I can’t wait to deal with. Either wait for the next update, or dive into it if it persists, but that will have to wait until tomorrow.
Perhaps start it from a terminal and see if you get any messages there when it shuts down. It might give someone on the forum some idea.
For your info, I am not. Buttery smooth as always (under its latest update).
Agree with this. I also just launched Snapshot and clicked on a few links and all seems good here.
Firefox 
OK, the problem persists so here is what happens:
[mr_ecks@MrEcks ~]$ vivaldi-snapshot
[1983:1983:1216/124710.359528:ERROR:sandbox_linux.cc(374)] InitializeSandbox() called with multiple threads i
n process gpu-process.
[2023:1:1216/124711.020649:ERROR:vivaldi_render_frame_observer.cc(38)] 0x19efb52166c0 VivaldiRenderFrameObser
ver::VivaldiRenderFrameObserver 0x19efb5136000
[2045:1:1216/124711.136459:ERROR:vivaldi_render_frame_observer.cc(38)] 0x19efb520d600 VivaldiRenderFrameObser
ver::VivaldiRenderFrameObserver 0x19efb52a7800
[2037:1:1216/124711.141025:ERROR:vivaldi_render_frame_observer.cc(38)] 0x19efb520c080 VivaldiRenderFrameObser
ver::VivaldiRenderFrameObserver 0x19efb5136e00
[2065:1:1216/124711.226242:ERROR:vivaldi_render_frame_observer.cc(38)] 0x19efb52e3720 VivaldiRenderFrameObser
ver::VivaldiRenderFrameObserver 0x19efb52a6100
[2075:1:1216/124711.343832:ERROR:vivaldi_render_frame_observer.cc(38)] 0x19efb52235a0 VivaldiRenderFrameObser
ver::VivaldiRenderFrameObserver 0x19efb52a3100
[2085:1:1216/124711.449534:ERROR:vivaldi_render_frame_observer.cc(38)] 0x19efb521f460 VivaldiRenderFrameObser
ver::VivaldiRenderFrameObserver 0x19efb52aa100
[2037:1:1216/124711.458455:ERROR:vivaldi_render_frame_observer.cc(38)] 0x19efb5217600 VivaldiRenderFrameObser
ver::VivaldiRenderFrameObserver 0x19efb53b9800
[2095:1:1216/124711.507499:ERROR:vivaldi_render_frame_observer.cc(38)] 0x19efb52167e0 VivaldiRenderFrameObser
ver::VivaldiRenderFrameObserver 0x19efb5136e00
[2037:1:1216/124711.946471:ERROR:vivaldi_render_frame_observer.cc(47)] 0x19efb520c080 VivaldiRenderFrameObser
ver::OnMessageReceived 0x19efb5136e00
[2117:1:1216/124715.615132:ERROR:vivaldi_render_frame_observer.cc(38)] 0x19efb5305600 VivaldiRenderFrameObser
ver::VivaldiRenderFrameObserver 0x19efb5136000
[1951:1951:1216/124716.216315:ERROR:CONSOLE(0)] “Unchecked runtime.lastError: The message port closed before
a response was received.”, source: chrome-extension://mpognobbkildjkofajifpdfhcoklimli/browser.html (0)
[1951:1951:1216/124716.216847:ERROR:CONSOLE(0)] “Unchecked runtime.lastError: The message port closed before
a response was received.”, source: chrome-extension://mpognobbkildjkofajifpdfhcoklimli/browser.html (0)
[1951:1951:1216/124716.217333:ERROR:CONSOLE(0)] “Unchecked runtime.lastError: The message port closed before
a response was received.”, source: chrome-extension://mpognobbkildjkofajifpdfhcoklimli/browser.html (0)
[2037:1:1216/124716.451629:ERROR:vivaldi_render_frame_observer.cc(38)] 0x19efb5b484a0 VivaldiRenderFrameObser
ver::VivaldiRenderFrameObserver 0x19efb56e7000
[2037:1:1216/124718.091707:ERROR:vivaldi_render_frame_observer.cc(47)] 0x19efb5b484a0 VivaldiRenderFrameObser
ver::OnMessageReceived 0x19efb56e7000
[2045:1:1216/124719.293966:ERROR:vivaldi_render_frame_observer.cc(38)] 0x19efb54ea880 VivaldiRenderFrameObser
ver::VivaldiRenderFrameObserver 0x19efb5137500
[2184:1:1216/124724.305889:ERROR:vivaldi_render_frame_observer.cc(38)] 0x19efb534b4c0 VivaldiRenderFrameObser
ver::VivaldiRenderFrameObserver 0x19efb5392300
Segmenteringsfel (minnesutskrift skapad)
[mr_ecks@MrEcks ~]$
This was short, but if you need something else I’ll paste bin it.
I won’t be pretending that I know what is going on. Sometimes starting an application on a blank slate could be revealing. You could rename Vivaldi’s config folder by appending .old or .back or some such to its name. Now you can launch the browser. If everything works as it should then the issue is within the config folder. Often it could be an extension acting up.
Thanks for the suggestion. I’ll try that later when I get back from work. If that doesn’t do the trick I’ll try reinstalling vivaldi-snapshot, and if that doesn’t work, I’ll try the ordinary Vivaldi as it’s in the repo now.
OK I must not have had the same version as you when I made my previous post. I checked updates about 20 minutes ago and got a new Snapshot. I just launched it, clicked to go to the Vivaldi forums, it sat on a blank page for about 2 seconds and then crashed. Just ran it from terminal and saved the out put. Will pastbin, post, and then create a help thread on the Vivaldi forums.
Thanks for doing that. I simply haven’t got the time to take care of things right now. All work and no play, until Christmas for me.
So, I got tired of waiting so I decided to take care of it. The latest (local) version was no longer available int he AUR so I just did a clean build of the old one from the AUR.
It’s probably not the proper way to deal with it, but I’m to tired to fuss about with downgrade… It did the trick at least. 
I’m back on Vivaldi, and I’m happy!
Edit: It works even after reboot, so I’m marking it as solved.