Very #serious #zeroday #cve for #chrome and #chromium https://chromereleases.googleblog.com/20.. Lodged a #ticket to #update and #upgrade the #ubuntu #deb #packages https://bugs.launchpad.net/ubuntu/+sourc.. Fingers crossed this happens soon.
Damn, #chrome #chromium has a pretty #serious #xss #vulnerability in a #newtab https://portswigger.net/daily-swig/dange..
Fuck me #google #chromium #chrome eats #ram ! 6GB for just 15 or so #tabs in a #web #browser ! Insanity. Meanwhile #firefox is running some 1k tabs and using 1.4GB of #ram - how on earth can #chromium get is so wrong?
This is why I always advise #ublockorigin to everybody I know: https://addons.mozilla.org/blog/ublock-o.. Unfortunately #google #chrome and #chromium disabled the functionality it uses *on purpose* because it was too effective at blocking their main #ad #revenue stream.
Seems to be some #css #parsing #bug in both #firefox *and* #chromium where multiple `counter-reset` calls somehow fail, but resetting multiple counters in the same line is perfectly fine. Very weird behaviour.
Glad so far that I didn't go with the #mainstream #mathml #js #library https://coffeespace.org.uk/projects/math.. It will surely bite me in the future as #chromium gains #nativesupport and new features are added, but a 10x size reduction is massive: https://www.igalia.com/2021/08/09/MathML.. It'll surely handle most of the complex #math #notation I'll ever need to throw at it.
Ouch, tonnes of #browser #extensions in #chrome and #chromium use shit tonnes of time to process! https://www.debugbear.com/blog/chrome-ex.. I imagine the story is the same in #firefox too. Currently I run #ublockorigin (block #as and #trackers ), #noscript (by default, disable all #js ) , #privacyredirect (avoid using #twitter , #youtube , #reddit , etc) and #waybackmachine (find archives of websites that fail to load).
Earlier I deleted the #snap version of #chromium from #ubuntu and installed the System76 version. It was already being buggy, but then it crashed and in all honesty I was completely hacked off with it. I ripped that piece of #sandbox #crapware out and it now seems to be running fine (or as fine as Chrome normally does).