@yngve said in Sadly, I will be leaving Vivaldi...:
@janrif Re VB-106321 we don't know what is triggering it, but it happens in Cookie related Extensions code (and it is an intended crash, an assert, by Chromium because the input values breaks the preconditions so severely that a crash would happen anyway). I would suggest that you test without extensions.
I don't know much about VB-106334, except that it is a duplicate of a another report, that seems to have some relation to dialogs (and thus could conceivably be related to the HTTP Auth crash I mentioned, but I don't know)
You might want to try some standalone installs and slowly test each component of your main configuration to see what works, and what doesn't. E.g. Some Extensions are known to cause trouble.
(And downloading old versions for any other reason than doing some testing for 5 minutes is !!NOT!! recommended; It is not a secure advice or action, @securely4024 ! )
@yngve Thank you for the follow up. I thought I was using the most current stable version but then I looked at Archive & I see 2 versions which is the latest that is listed, with the same number but different sizes (which is confusing) and I am on an even later ver# which is identified as stable (also confusing).
In this case, It was impossible for me to test the troubled version bc it kept crashing immediately on startup and I hadn't thought of installing an older version so I could see what might be going on. The test steps that @danial posted was extremely helpful & started me on the road to recovery.
I uninstalled 2 extensions that @daniel noted from the data dump & everything is ok so far. I am now working w stand alone version(s) as you (& others) have suggested so there is no confusion there.