Vivaldi failed to launch on macOS 14
-
@micen I'm on a Mac (as noted in my sig, an i5 Catalina system...) and have relied on Vivaldi as my primary browser since version 3.7. While there have been occasional glitches -even one goof!- the browser has been dependable for me, despite an increasing array of new features!
I hope your problems with Vivaldi are sorted out and solved soon: You're missing out on an exceptional experience!
-
@xyzzy said in Vivaldi failed to launch on macOS 14:
@bulkington When you say uninstall/reinstall, did you just remove and reinstall Vivaldi.app in /Applications or did you also attempt to either clean the profile or perform a full reset of Vivaldi
So is deleting all settings every few weeks the accepted solution to this problem? I'm not sure if I want to do this in the long run - even if it worked again.
-
@SchlimmGenug said in Vivaldi failed to launch on macOS 14:
@xyzzy said in Vivaldi failed to launch on macOS 14:
@bulkington When you say uninstall/reinstall, did you just remove and reinstall Vivaldi.app in /Applications or did you also attempt to either clean the profile or perform a full reset of Vivaldi
So is deleting all settings every few weeks the accepted solution to this problem? I'm not sure if I want to do this in the long run - even if it worked again.
Is just asking what the user did.
-
This post is deleted! -
@Zalex108 said in Vivaldi failed to launch on macOS 14:
@SchlimmGenug said in Vivaldi failed to launch on macOS 14:
@xyzzy said in Vivaldi failed to launch on macOS 14:
@bulkington When you say uninstall/reinstall, did you just remove and reinstall Vivaldi.app in /Applications or did you also attempt to either clean the profile or perform a full reset of Vivaldi
So is deleting all settings every few weeks the accepted solution to this problem? I'm not sure if I want to do this in the long run - even if it worked again.
Is just asking what the user did.
So is there a better solution to this problem that has been going on for a few months?
-
@SchlimmGenug said in Vivaldi failed to launch on macOS 14:
So is there a better solution to this problem that has been going on for a few months?
well, ... maybe ...
Please install a separate snapshot from our Desktop Snapshot stream at https://vivaldi.com/blog/desktop/snapshots/ . See if that reproduces the issue, either immediately, or after repeating the steps that may have triggered it, or after copying the entire profile from your Stable environment.
The current snapshots are based on Chromium 120, same as the current Stable Vivaldi v6.5.
However, one of the next snapshots (probably not the next scheduled one) will have the new Chromium 122 code base, which includes a new feature (which we've enabled), introduced in Chromium 121, that is supposed use a new system for the camera that bypass the entire code path that is causing the (suspected) camera device enumeration crash.
We would be very interested (and I am sure the Chromium team is, too) in learning if that does fix the issue.
-
FYI, The first Snapshot based on Chromium 122 was released last week. Please see if that solves the crasher problem related to device/Camera enumeration .
-
If I worked with Linux I would certainly be happy with such experiments. Under MacOs I expect things to work. Common sense also says that if other Chromium-based browsers don't have this problem, it probably can't be due to Chromium. There's also the problem that the window appears somewhere on the screen every time you start Vivaldi since... more than a Year - do you also wait until Chromium sort that out?
-
@SchlimmGenug If you read my posts above, you will learn that one reason Chromium developed the new feature is that they had reports about the issue almost a year ago (one of the affected users was a Google employee), and that the problem was so deep inside MacOS that it wasn't practical to discover how to fix it (Apple can make mistakes, too; there was references to reporting a possible related issue to Apple all the way back in OSX 10.15 beta).
-
Then all other browser manufacturers have probably found solutions to the problem since Catalina.
-
@SchlimmGenug The point is that the problem was reported happening to a Google(!) employee less than 12 months ago. If you are interested, see the bug report
And the relevant code is entirely upstream Chromium, we made no changes to it. We suspect it has something to do with MacOS drivers for the Camera in certain system configurations, but AFAICT even Google never figured out what the trigger was (and none of our internal Mac users or the volunteers was ever able to reproduce).
So, no, they did not find a solution for it using the old Chromium code, they had to write an entirely new feature which has been rolling out to about 1% of Chrome users in the past month or so, and they are now preparing to roll it out to all users.
The currently released v6.6 Snapshot builds based on Chromium 122 include this new feature and it is enabled by default, and we (and probably the Chromium team) are very interested to discover if that fixes the crasher for users that have the crash.
-
Yep just had this happen to me. MBA m1 2020, i right clicked a link and click open in Private Window and then had the app freeze. Force closed it. Wouldn't open again, same as others here.
Uninstall reinstall did nothing. Even updating macOS to sonoma 14.3.1 didn't help. Someone in this thread said to get Appcleaner and I used that, now Vivaldi works again.
This was incredibly annoying and I lost a lot of work, and extension data. Given this bug has been around for ages, and continues to occur, I'm hoping the dev team knows whats causing it
-
The currently released v6.6 Snapshot builds based on Chromium 122 include this new feature and it is enabled by default, and we (and probably the Chromium team) are very interested to discover if that fixes the crasher for users that have the crash.
Just had this problem when I updated to 3206.63, vivaldi refused to start. Same specs as all the previous posters here.
Installed snapshot 3271.35 and copied the profile folder directly over, it's working for now.
Not too happy as wasted 3-4 hours trying to sort this out, hopefully there isn't such a insidious bug ever again, as I'm finding it hard to trust vivaldi for anything critical.
-
Installed snapshot 3271.35 and copied the profile folder directly over, it's working for now.
Appears that v6.5 messed up the Preferences file when it was updating, leading to this problem.
But v6.6 did not think the file was corrupted, it started up just fine. Subsequently, copying the Preferences file, back to the profile folder in v6.5, fixed the problem with v6.5 too. I didn't change any prefs in the snapshot, just browsed normally for a few hours.
I believe it's the Preferences file because restoring the original "corrupted" file from the profile backup caused the problem to occur again, but restoring any other files in the profile folder didn't stop v6.5 from starting up.
Note that I have no devices attached to my macbook other than a bluetooth mouse.
Unfortunately this is probably not much help to the devs, but then again I don't see why a single file containing some settings should cause the whole program to just abort and not start up.
Well I now have two vivaldi installations and I learned a bit about how the profile folder works, but a whole day of productivity was lost
-
FYI, The v6.6 Stable released today includes the potential fix for the (presumed) camera related device enumeration crash issue.
Please test, and report back if it solves the problem
-
Still the same issue, and now, snapshot version crashes again too
-
@kr0n0s1024 Then reporting a new issue and submitting crashdumps might be useful.
-
Too late, I was tired of not being able to open the browser and uninstalled everything with cleanmymac. I tried installing just the snapshot without syncing the profile, and it crashed 2 times. so, I synced the profile. It is true that with the snapshot, it doesn't crash as many times as with the normal version, but it does it from time to time. I activated the log sending in the new version.
-
@kr0n0s1024 Those crashes could be something completely different from what was discussed earlier in this thread, which is why we need crashdumps to discover the reason for the crash.
Even if the crashdumps where uploaded, it is still useful for users to separately upload the log in a bug report, since it is then possible to give more information.
-
I submitted the report and sent the dmp file to the team.