Vivaldi Snapshot re-opened on its own after a crash



  • So as the title states, the application re-opened itself after a crash (one that I very intentionally caused in order to reproduce). Before the crash, I was running the snapshot in the "standalone mode" that we currently have for mac, but after the crash the snapshot version restarted itself, and as I did not start it in "standalone mode", it used my regular profile.

    In short, is my regular profile completely screwed now that it has been opened by a snapshot version of Vivaldi, or can I save it somehow?



  • @AltCode Hard to tell, you gotta try it. I used to have a standalone stable build, but I quit running one because it destroyed my snapshot profile once. It's best to make regular updates of your profile to have something to revert to. Are you running time machine backups or do you clone your macOS install regularly? – Switching to a backup profile would be the safe option, provided it isn't old.



  • @luetage Well, so far everything appears to be working fine, but it will be hard to tell for sure. Last time something like this happened, Vivaldi lost the ability to save passwords. Sadly I did not make any kind of backup; I tried setting up time machine backups multiple times, but they always failed to set up, so I gave up on that. Maybe I'll try again.



  • @AltCode I wouldn't use time machine, better clone your macOS install to another drive on a regular basis, something between daily and weekly. You can do it in terminal, or with a dedicated application. Comes in handy when your ssd/harddrive fails or somehow gets corrupted.


  • Moderator

    @AltCode I've triggered this weird double-crash before just by undocking dev tools.

    By the way, rather than reverting back, another option would have been to continue using your main profile with the 2.4 Snapshots and then switch to Stable when Vivaldi 2.4 gets released. (To anybody else reading, it's because of situations like this that I don't recommend using a Standalone launcher or having multiple Vivaldi versions installed on macOS.)

    You'll probably still have some additional clean-up that needs to be done.

    Double-check your Applications folder to make sure that you don't have a "Chrome Apps" folder containing a Vivaldi.app Chrome app launcher. If you do, you'll need to clean this up, and you'll also need to remove the corresponding .sfl file from ~/Library/Application Support/com.apple.sharedfilelist/com.apple.LSSharedFileList.ApplicationRecentDocuments/

    ... and if you still have extra Vivaldi launchers in Launchpad, you may also need to reset Launchpad back to its defaults with:

    $ defaults write com.apple.dock ResetLaunchPad -bool true; killall Dock


  • @xyzzy said in Vivaldi Snapshot re-opened on its own after a crash:

    By the way, rather than reverting back, another option would have been to continue using your main profile with the 2.4 Snapshots and then switch to Stable when Vivaldi 2.4 gets released. (To anybody else reading, it's because of situations like this that I don't recommend using a Standalone launcher or having multiple Vivaldi versions installed on macOS.)

    I wish I had thought of that.

    Anyways, I have encountered a problem. Any time that I try to delete a bookmark, Vivaldi crashes. However, I tried creating a new profile to see if this still happened, and it did. Could there be something else that I missed or it this just a bug in the stable version?


  • Moderator

    @AltCode I can confirm the crash when deleting a bookmark, and that it was caused by reverting back to Vivaldi 2.3 (Stable) from the 2.4 Snapshot.

    I confirmed this by performing a new/clean Stable install, importing bookmarks, deleting bookmarks, moving them, etc. and confirming that everything worked fine. Upgrading to 2.4 RC3 also worked, but reverting back to 2.3 was problematic.

    The semi-good news is that the "delete bookmark" crash went away after I upgraded back to 2.4. Unfortunately, I don't know what going from 2.3 to 2.4 to 2.3 to 2.4 did to the profile or how this will impact future stability.


Log in to reply
 

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