Florian Bruhin

Hm, I also wonder how much this is related to a second corruption nobody has been able to explain so far, #5606 (and the issues linked there). @nancym, do you...

Looks like this still sometimes happen (though rarely) on Linux: https://termbin.com/f9l1

With 7d8fd507924309227ebb6c11c3d32cb0b013d238 I've now introduced a new `qt.workarounds.remove_service_workers` setting which can be set to `true` to nuke the service workers directory on every start. I'm not really happy with that...

In [this Reddit thread](https://www.reddit.com/r/qutebrowser/comments/n1uoay/corrupted_basedir/), u/Cognhuepan says they're on Fedora 34 and: > Okay, I've just installed upgrades, and the system forced me to restart to install these updates closing qutebrowser...

Another possible lead from [this reddit thread](https://www.reddit.com/r/qutebrowser/comments/nrhxqt/browser_crashes_loading_websites/): > The websites I had open while testing it included Twitter, Reddit, Youtube, and Google. and then shutting down with `shutdown now` on...

So it looks like `:set qt.workarounds.remove_service_workers true` is an appropriate workaround for this for many people - yet most don't know about it obviously, and I continue to get many...

> Ongoing work regarding #5356 > > [...] Yay! I'd suggest getting this (CSS selector) in first, and then taking the others step by step. > * What to do...

I'll be quite busy the next 1-2 weeks as well and then be on holidays for another 1-2 weeks. Right now it doesn't look like in a mergable state since...

Sorry for the radio silence, I dropped the ball on this and probably didn't remember your question comment after the holidays :sweat_smile: The QtWebKit backend is pretty much on life...

Should probably be rebased now that #7096 is in.