Crash on launch of latest Vivaldi version on Mac

  • I just downloaded and installed the latest Vivaldi version (1.9.818.44) on my 27" iMac with macOS 10.9.5, but each time I try to launch it, it crashes instantly. Anyone having the same issue? I can provide the crash dump if needed.

  • @eb303 Ouch! I haven't run into any issues on OS X 10.11.6. My initial thought was that something could have gotten corrupted in your Vivaldi profile... perhaps a problem with your Top Sites file or a session-related issue. However, it's also possible that it could be a problem specific to Vivaldi running on Mavericks, although yours is the first report that I've seen.

    From your previous posts, I see that you've been using Vivaldi for quite a while. Have you done any steps yet to either "clean" or reset your profile?

  • @xyzzy No, I haven't. But I just tested to launch the latest Vivaldi version on an account where I don't think I've ever run it at all, and same issue: it crashes at once.
    However, I'll try to just download a clean copy of the latest version and not use the automatic update, maybe it will solve the issue. I'll post a new message here once I've done that.

  • @xyzzy That was it: I downloaded the full version without using the automatic update, copied the application bundle to the Applications folder, and now the new version works without problem. I noticed the downloaded sizes were different between the 2 apparently: almost 70Mb for the full disk image, and only around 50 Mb for the update. I read you had a new policy of updates by delta rather than downloading the whole thing each time. Maybe the problem is there?

  • @eb303 Wow, that's strange. Older (but still not from all that long ago) versions of the Sparkle update framework did have some bugs and it's possible that this could have been the problem. I'm just surprised that the update process succeeded but your Vivaldi application clearly had issues.

    If you ever suspect a problem with Vivaldi, or any other application, you can check the integrity of the application bundle with the following command from a Terminal prompt:

    $ spctl -a -vv /Applications/

    ... and get details about the bundle's digital signature with:

    $ codesign -d --verbose=2 /Applications/

    I'm glad to hear that everything is working for you again.

  • @xyzzy Except sadly, I spoke too fast: I still have issues. Basically, everything seems to be fine on the administrator account where I installed Vivaldi. But if I try on any other account on my Mac, it still crashes on launch. I tested with 3 different accounts, and the crash happens on all 3. But it works on my main administrator account. Could it be a permission issue, maybe?

    I also ran the 2 commands you gave me and here are the results:

    pc6:~ ericb$ spctl -a -vv /Applications/
    /Applications/ accepted
    source=Developer ID
    override=security disabled
    origin=Developer ID Application: Vivaldi Technologies AS (4XF3XNRN6Y)
    pc6:~ ericb$ codesign -d --verbose=2 /Applications/
    Format=bundle with Mach-O thin (x86_64)
    CodeDirectory v=20200 size=203 flags=0x800(restrict) hashes=3+3 location=embedded
    Signature size=8544
    Authority=Developer ID Application: Vivaldi Technologies AS (4XF3XNRN6Y)
    Authority=Developer ID Certification Authority
    Authority=Apple Root CA
    Timestamp=26 Apr 2017 18:44:18
    Info.plist entries=34
    Sealed Resources version=2 rules=12 files=492
    Internal requirements count=1 size=172

    Apparently, no error in there, at least none I can see. Does it look fine to you?

  • Crashes at startup on any non-admin account, whether the user has previously run Vivaldi or not.

    Before chancing upon this thread I thought that the update process had gone awry and downloaded and installed a new copy, to no avail.

    MacOS 10.12.4

    Crashed Thread: 0 Dispatch queue:

    Exception Type: EXC_CRASH (SIGABRT)
    Exception Codes: 0x0000000000000000, 0x0000000000000000
    Exception Note: EXC_CORPSE_NOTIFY

    Application Specific Information:
    abort() called

    Thread 0 Crashed:: Dispatch queue:
    0 libsystem_kernel.dylib 0x00007fff8c3e2d42 __pthread_kill + 10
    1 libsystem_pthread.dylib 0x00007fff8c4d05bf pthread_kill + 90
    2 libsystem_c.dylib 0x00007fff8c348420 abort + 129
    3 com.vivaldi.Vivaldi 0x0000000101ac1c89 main + 233
    4 libdyld.dylib 0x00007fff8c2b4235 start + 1

    Thread 0 crashed with X86 Thread State (64-bit):
    rax: 0x0000000000000000 rbx: 0x0000000000000006 rcx: 0x00007fff5e13eb28 rdx: 0x0000000000000000
    rdi: 0x0000000000000307 rsi: 0x0000000000000006 rbp: 0x00007fff5e13eb50 rsp: 0x00007fff5e13eb28
    r8: 0x0000000000000040 r9: 0x00007fff95207040 r10: 0x0000000008000000 r11: 0x0000000000000206
    r12: 0x0000000000000001 r13: 0x00007ff286800a00 r14: 0x00007fff952233c0 r15: 0x00006080000d9ad0
    rip: 0x00007fff8c3e2d42 rfl: 0x0000000000000206 cr2: 0x00007fff8c4cd9ba

    Logical CPU: 0
    Error Code: 0x02000148
    Trap Number: 133

  • Holy crap! Confirmed! Looks like a permissions issue. If an admin installs Vivaldi in /Applications, some of the files are not accessible by other users making it impossible for them to launch Vivaldi.

    I purged my Vivaldi test installation and reinstalled Vivaldi the "normal/proper way" into /Applications. When I ran it as an admin, it worked fine. When I tried running it from my normal account, it would not even execute.

    I then tried launching it from Terminal:

    $ open /Applications/
    LSOpenURLsWithRole() failed with error -10810 for the file /Applications/

    Not good... Lets's keep digging... As a non-admin, I tried to list the directory tree and got a bunch of "Permission denied" errors:

    $ ls -laR /Applications/ | more
    [...stuff deleted...]
    ls: Vivaldi Framework.framework/Helpers: Permission denied

    However, from the admin account, apart from the permissions issue, the Vivaldi build checked out okay:

    $ codesign --verify --verbose=4 --deep --strict /Applications/
    /Applications/ valid on disk
    /Applications/ satisfies its Designated Requirement
    $ codesign -d --verbose=2 /Applications/ 
    Format=app bundle with Mach-O thin (x86_64)
    CodeDirectory v=20200 size=203 flags=0x800(restrict) hashes=3+3 location=embedded
    Signature size=8544
    Authority=Developer ID Application: Vivaldi Technologies AS (4XF3XNRN6Y)
    Authority=Developer ID Certification Authority
    Authority=Apple Root CA
    Timestamp=Apr 26, 2017, 12:44:18 PM
    Info.plist entries=34
    Sealed Resources version=2 rules=12 files=492
    Internal requirements count=1 size=172
    $ spctl -a -vv /Applications/ 
    /Applications/ accepted
    source=Developer ID
    origin=Developer ID Application: Vivaldi Technologies AS (4XF3XNRN6Y)

    So... how could this have made it through QA?

    I always use my Mac as a non-admin user and typically install Vivaldi into a personal Applications directory for testing. Vivaldi didn't fail for me because I owned (and had permission to access) all of the files in the Vivaldi bundle.

    Other users who use admin accounts day-to-day would not have encountered any problems either.

    As far as I can tell, the Vivaldi application itself seems to be okay. However, I'm guessing that some of the permissions were simply not set correctly by the build scripts before generating the Vivaldi.1.9.818.44.dmg disk image.

    Bug filed: VB-28028

  • @Vivaldi-Team I fixed the permissions on the symlinks within my local install and can now launch Vivaldi from my regular (non-admin) account. This doesn't impact the signing of the application bundle so a quick fix can be posted... I could do it but would prefer that you (Vivaldi) post an "official" fix.

    If (by happenstance) a 1.9-stable update is imminent, please double-check the file permissions in the bundle before release.

    Edit: Looks like this affects the Vivaldi 1.10 snapshot builds on macOS as well.


  • @xyzzy I fixed the permissions for the symbolic links too and it looks like it worked indeed. Thanks for the help!
    Just in case someone would like a quick fix, just open a Terminal as an administrator and run the command:
    find /Applications/ -type l -print0 | xargs -0 chmod -h a+rx
    That's what fixed the issue for me. But I agree that an official fix would be much nicer…

  • @eb303 Thanks for picking up on the hint. :-) In this case, it was fortunate that the fix was to apply the same permission change to every symlink in the bundle.

  • FYI, I also raised this issue as feedback to the Vivaldi 1.10.834.9 Snapshot release. Vivaldi replied that they "are fully aware if it."

    Here's a link to my post:

    You can also read the full thread (it's at the top of the comments section) here:

    Hopefully a fix is in the works.

  • FYI, this issue was fixed in the Vivaldi 1.10.838.7 snapshot that was released earlier today. Unfortunately, Vivaldi 1.9 is still broken, and also in need of updating because Chromium 58.0.3029.110 just got released this afternoon too.

  • @xyzzy OK, thanks a lot for the updates. :smile: As long as the dirty hack works for v1.9, I'm happy, though. :wink: And at least, the developers are aware of the issue now, so I guess the next release will have it fixed, that's the most important.

  • Mac builds are now fixed on both the Snapshot and Stable channels. If you don't have any objections, I'm marking this thread Resolved.


  • @xyzzy Downloaded and installed the latest version: it works indeed, no problem at all. :smiley: Thanks again!

Log in to reply

Looks like your connection to Vivaldi Forum was lost, please wait while we try to reconnect.