Hello, The Debian patch for #963548 https://salsa.debian.org/mimi89999/chromium/-/blob/ece23b4ca107cd968ac9a409f40eb11edf8a0266/debian/patches/fixes/serviceworker-double-destruction.patch is clearly in upstream 87.0.4280.88: https://source.chromium.org/chromium/chromium/src/+/refs/tags/87.0.4280.88:content/browser/service_worker/service_worker_container_host.cc;l=671-679
I also think that it might be an upstream bug, but can't confirm unless tested and reproducible in Google Chrome. Michel Le Bihan Le mercredi 23 décembre 2020 à 04:10 -0600, Boyd Stephen Smith Jr. a écrit : > On Wednesday, December 23, 2020 3:49:06 AM CST Boyd Stephen Smith Jr. > wrote: > > On Wednesday, December 23, 2020 2:38:32 AM CST Boyd Stephen Smith > > Jr. wrote: > > > I got a crash (attached) > > > > Looks like > > https://bugs.chromium.org/p/chromium/issues/detail?id=1135070 to > > me, which has a fix, but I haven't yet figured out what release(s) > > the fix > > made it into. > > Doesn't look to me like it has made it into a release at all, but I'm > just > using the Git tools to navigate the repository, not all the depot > tools. > > ---8<--- > bss@monster % git tag -l --contains > f27ad210062f61d06eb782214ee4fc8c19a1725b > bss@monster % git branch -r --contains > f27ad210062f61d06eb782214ee4fc8c19a1725b --list > origin/HEAD -> origin/master > origin/lkgr > origin/lkgr-android-internal > origin/lkgr-ios-internal > origin/master > --->8--- > > So, I guess it's an "upstream" bug?
