On Tuesday, December 22, 2020 5:26:04 PM CST Boyd Stephen Smith Jr. wrote: > On Tue, 22 Dec 2020 23:43:23 +0100 Michel Le Bihan <mic...@lebihan.pl> wrote: > > I was not able to reproduce those crashes. > > That's unfortunate. I'm up to 50 just today. I'm probably going to have to > downgrade to 83 at least until there's another update.
Downgrading was a mixed bag (browser was stable, but audio/video stopped working (!)) . So, I tried again with 87. Rather than just disabling my extensions, I tried from a brand-new profile and an empty cache. So far, I'm not able to reproduce the crashing on the new profile. Unfortunately, I have about a half-dozen extensions that have at least some configuration that isn't synchronized anywhere else, so I need to go back to 83 and the old profile, dump/export/backup all their settings to a file (or take notes), then go back to 87 and the new profile and restore/import/apply all those settings in the new profile. All my extensions were pulled down during the Google Sync and ran fine on 87 for roughly an hour -- that's twice as long as my longest browser session for version 87 on the old profile. I still convinced this is a bug -- nothing in my profile should cause a SEGV, ref_count violation, or corrupted double-linked list. But, there's at least a workaround, that I'm going to take advantage of, to create a new, blank profile and either sync or manually import (or likely a combination of both) all your settings into the new profile. It's not going to be a kind experience for people upgrading from buster to bullseye, especially since the crashes make it hard to export settings from your old profile. -- Boyd Stephen Smith Jr. ,= ,-_-. =. b...@iguanasuicide.net ((_/)o o(\_)) Twitter: @DaTwinkDaddy `-'(. .)`-' http://iguanasuicide.net/ \_/
signature.asc
Description: This is a digitally signed message part.
