Vivaldi failed to launch on macOS 14

cemarriotto

It did happen again this evening. I tried launching from Terminal to capture the output.

❯ ./Vivaldi
[53261:259:1112/234121.305529:ERROR:downgrade_utils.cc(51)] /Users/(userName)/Library/Application Support/Vivaldi/Snapshots/6.4.3160.42 -> /Users/(userName)/Library/Application Support/Vivaldi/Snapshots.CHROME_DELETE/6.4.3160.42: Directory not empty (66)
[53261:259:1112/234121.325395:ERROR:policy_logger.cc(154)] :components/enterprise/browser/controller/chrome_browser_cloud_management_controller.cc(163) Cloud management controller initialization aborted as CBCM is not enabled.
[1112/234121.641862:WARNING:crash_report_exception_handler.cc(235)] UniversalExceptionRaise: (os/kern) failure (5)
[53268:14851:1112/234121.643601:ERROR:ssl_client_socket_impl.cc(975)] handshake failed; returned -1, SSL error code 1, net_error -3
[1]    53261 trace trap  ./Vivaldi

A second try, just to be sure, still failed:

❯ ./Vivaldi
[53286:259:1112/234133.130605:ERROR:downgrade_utils.cc(51)] /Users/(userName)/Library/Application Support/Vivaldi/Snapshots/6.4.3160.42 -> /Users/(userName)/Library/Application Support/Vivaldi/Snapshots.CHROME_DELETE/6.4.3160.42: Directory not empty (66)
[53286:259:1112/234133.147642:ERROR:policy_logger.cc(154)] :components/enterprise/browser/controller/chrome_browser_cloud_management_controller.cc(163) Cloud management controller initialization aborted as CBCM is not enabled.
[1112/234133.465613:WARNING:crash_report_exception_handler.cc(235)] UniversalExceptionRaise: (os/kern) failure (5)
[53293:12035:1112/234133.469341:ERROR:ssl_client_socket_impl.cc(975)] handshake failed; returned -1, SSL error code 1, net_error -3
[53293:12035:1112/234133.470154:ERROR:ssl_client_socket_impl.cc(975)] handshake failed; returned -1, SSL error code 1, net_error -3
[1]    53286 trace trap  ./Vivaldi

Taking a look at the mentioned Snapshot directory:

❯ cd Snapshots.CHROME_DELETE
❯ ls -la
total 0
drwx------@  5 (userName)  staff   160 Nov 12 23:41 .
drwx------  50 (userName)  staff  1600 Nov 12 23:41 ..
drwx------@  6 (userName)  staff   192 Nov 12 23:41 6.4.3160 (1).42
drwx------@  6 (userName)  staff   192 Nov 12 23:41 6.4.3160 (2).42
drwx------@  6 (userName)  staff   192 Nov 12 22:03 6.4.3160.42

After moving the Snapshots.CHROME_DELETE folder out of the tree, it still didn't work:

❯ ./Vivaldi
[54152:259:1112/234937.127396:ERROR:policy_logger.cc(154)] :components/enterprise/browser/controller/chrome_browser_cloud_management_controller.cc(163) Cloud management controller initialization aborted as CBCM is not enabled.
[1112/234937.442572:WARNING:crash_report_exception_handler.cc(235)] UniversalExceptionRaise: (os/kern) failure (5)
[1]    54152 trace trap  ./Vivaldi

After removing the Default/Preferences file, opening the app worked... It seems to have produced the same error message when it was not working, though.

❯ ./Vivaldi
[54751:259:1112/235047.161649:ERROR:downgrade_utils.cc(51)] /Users/(userName)/Library/Application Support/Vivaldi/Snapshots/6.4.3160.42 -> /Users/(userName)/Library/Application Support/Vivaldi/Snapshots.CHROME_DELETE/6.4.3160.42: Directory not empty (66)
[54751:259:1112/235047.182048:ERROR:policy_logger.cc(154)] :components/enterprise/browser/controller/chrome_browser_cloud_management_controller.cc(163) Cloud management controller initialization aborted as CBCM is not enabled.
[54751:259:1112/235047.889551:ERROR:history_private_api.cc(444)] Unable to open database.
[54751:259:1112/235047.944450:ERROR:CONSOLE(1)] "Uncaught (in promise) TypeError: Cannot read properties of undefined (reading 'reduce')", source: chrome-extension://mpognobbkildjkofajifpdfhcoklimli/bundle.js (1)

Let me know if I can help troubleshoot in any other way when it reoccurs.

Chas4

In the macOS console it might have the crash reports and might also have other info

For snapshot there is an update to that beta version (I did not see a fix listed for macOS 14 but would not hurt to try if you are testing snapshots)

mhowie

@Chas4 said in Vivaldi failed to launch on macOS 14:

In the macOS console it might have the crash reports and might also have other info

For snapshot there is an update to that beta version (I did not see a fix listed for macOS 14 but would not hurt to try if you are testing snapshots)

The problem isn't there with the Snapshot builds- only the release version installed on top of one's existing Vivaldi build/files/settings/etc. Weird.

Snapshot builds open and run as expected. Release builds choke immediately upon starting and crash within a second or so.

If I could retrieve all my settings I'd start fresh with a new release build. Sadly, I can't open Vivaldi any longer in order to save everything. Very disappointing.

GenericRandom54

Same issue. Closes and then won't reopen.

Running macOS 14.1.1 (23B81)
M2 MacBook Pro (2023)
Vivaldi 6.4.3160.42
Extensions 1password, BetterTTV, Omnivore

nedhamson

When, how will these problems be fixed?!? I have not updated my M1 MacBookAir for fear, I will lose access to Vivaldi. Is Vivaldi working on this or not? Nearly a month now -

jane.n

@nedhamson I don't know about the progress of the issue, but I know the devs have been looking into it.

nedhamson

@jane-n I have to wonder why there has been so little communication - there must be a lot of users waiting for a solution.

slajerek

I guess this may be related or duplicate: https://forum.vivaldi.net/topic/92594/vivaldi-crashes-at-startup

jane.n

We believe we have fixed the issue. It needs to go through some testing to verify the fix and then we can get it to you.

Ruarí

Well we have fixed an issue (related to a failure in the update checker with bad data) but I am not at all convinced that everyone is talking about the same issue. Indeed some of the comments made would imply that it is not the same issue at all †. If you have not logged a bug with a crashlog, please do because "I have a crash on startup with Ventura" is not enough to information work on when the vast majority of users do not encounter this, and the only such crash we can reproduce we have fixed.

This (or these) issues are not as reproducible as those affected might think. A crashlog will give us clues and help clarify if you are having the same issue or totally different issues. (If you already logged a bug with a crashlog, thanks!)

https://help.vivaldi.com/desktop/troubleshoot/reporting-crashes-on-macos/

Post back here with your bug number if you like and to show you have logged it with a crash dump file.

Anyway, regarding the bug @jane-n mentions that we just fixed internally, a good way to see if it is the thing you are encountering is to provide the output of these two commands (paste them into Terminal.app and copy the output)

defaults read com.vivaldi.Vivaldi SULastCheckTime

and

defaults read-type com.vivaldi.Vivaldi SULastCheckTime

† The bug we fixed would cause a crash irrespective of Vivaldi Settings/Preferences and it would be instant (not seconds later). Clearly some of the reports here do not result in a crash with clean Vivaldi Settings/Preferences and those who crash after a few seconds also have something different.

Ruarí

… there must be a lot of users waiting for a solution.

@nedhamson There are a grand total of 7 bug reports in our bug tracker related to a crash on startup that appear to be from Sonoma (or it is listed in meta data for the crash report). Not all of them have a crashlog attached. Either almost nobody is logging their bug on our bug tracker or these issues are extremely uncommon. Again… if anyone is getting a startup crash and has not yet logged a bug with a crash .dmp attached, please do.

Ruarí

@ericole @kr0n0s1024 @slandolt @Al1972 @Sootygull @cemarriotto @GenericRandom54 Have you logged this in the bug tracker and attached a crash log? If yes could you tell me the numbers for your bug reports.

@mhowie I see you mentioned you did log it. Can I have your number. It should be in the email you got back when you submitted it?

@nhave Your bug sounds different if I read you correctly as it is not happening on launch but later? In any case did you log a bug and attach a crash report and if so what is the bug number, so I can compare the crashlog with the others.

@wisebeach9763 Your issue is clearly not the same. You are not getting a crash but high CPU/Freeze. Nonetheless have you logged it and if so what is your bug number? You also mentioned a preference file that causes Vivaldi to freeze. This may contain personal information but if you are willing please attached it to any bug report.

@hfhgbfjsyfbai Your description is odd because you say reinstall but you are not deleting prefs?? If so a reinstall should not make any difference at all. You mention a bug report, what is the number.

@nedhamson You seem to be holding back upgrading your OS because you think this is a common problem. It is not. We have 7 reports in our tracker and 11 people here (several of whom seem to have completely different issues). Also there is overlap between the two as some here have said they logged bug reports. The overwhelming majority of users are not having a crash on Startup on Sonoma. We probably have more Sonoma machines owned by Vivaldi employees working just fine, than known reports as of right now.

@gwiazda90 This thread is about a crash on startup on Sonoma. I would therefore not assume you have the same issue. In any case, the advice would be the same, submit a bug report with a crashlog.

@davide.aversa Your issue, which is now resolved was probably unrelated to the others and fixed after one of the minor updates, which get applied on browser restart.

slandolt

defaults read com.vivaldi.Vivaldi SULastCheckTime
2023-11-21 14:56:11 +0000

defaults read-type com.vivaldi.Vivaldi SULastCheckTime
Type is date

@Ruarí

Just created a new bug report VB-101836, added the 4 most recent .dmp, thanks!

Ruarí

@mhowie said in Vivaldi failed to launch on macOS 14:

Perhaps it's such a small subset of their user base that the resource required to overcome the problem doesn't make sense to allocate and it's easier to just let users migrate away.

You are only partially correct. Yes my impression is it is very few users (I could be wrong but that is the way it seems looking at the bigger picture than just this one thread of a handful of people).

The reason it is not fixed is that there is very little information to work on so far and AFAIK, I have never personally seen a machine with the crash you describe nor can I reproduce it at will, as you apparently can.

Here is a screenshot from the machine I am running right now. It is running stable Vivaldi on Sonoma and it is not crashing and I do not expect it will crash anytime soon as I am missing key differences things you have changed in Vivaldi or macOS.

Also, of those that have provided crash reports not all the same crash and at least some of the crashes have been fixed already. So this is not this one big issue that everyone has. Rather it is likely 2-3 different issues that very few users are hitting and none of them are (yet) well understood by the team.

Ruarí

@slandolt Ok, you do not have the same bug we just fixed internally based on what you provided from those commands, so sadly the fix we have lined up will not help you. I will process your crashlogs and look at them tomorrow.

Sootygull

@Ruarí I have just had an Apple Update,so now at Sonoma 14.1.1 (23B81) and Vivaldi works fine now.

Ruarí

@Sootygull Good to hear. Thanks for coming back to update!

nedhamson

@Ruarí Hope you are correct... guess I will upgrade.

Ruarí

@nedhamson said in Vivaldi failed to launch on macOS 14:

Hope you are correct... guess I will upgrade.

I am literally running Vivaldi 6.4.3160.44 on macOS Sonoma 14.1.1 right now and using it to type this message in reply to you.

hfhgbfjsyfbai

@Ruarí Thanks for coming back to me. I use an app uninstaller so it clears out the folders in /Application Support. A fresh install made things work for a short time, but the problem would return.

Bug reports were VB-100163 & VB-101442.

I've not been able to use Vivaldi since my last post, but I've just downloaded it again and will see how it goes.