People ragging on the only viable browser solution we have… Firefox is rock solid, fast, tweakable, and keeps me as safe as any browser and my configs/habits can. I don’t care if management eats babies.

I use it on debian with celenity phoenix and a few about:config tweaks, also tweak’d the theme a bit. Extensions: ublock origin, sponsorblock, localcdn, consent-o-matic, containers, keepassxc-browser, and sometimes jshelter.

web browsing: solved

    • o_O@lemmy.today
      2·
      23 hours ago

      Here is a link to one of the bug reports: https://bugzilla.mozilla.org/show_bug.cgi?id=1897006

      Said report was closed down and presumed “fixed” but I still encounter this issue on the latest stable.

      When you know what to search for you’ll find numerous users reporting similar behaviour on Reddit and other social platforms going back multiple years.

      If I were more invested I would keep submitting bug reports and memory dumps in the hopes that it may once and for all get stomped. But I’ve made the leap back to chromium and can’t justify the time. I realise that this is a major issue but one that only affects a small percentage of users, likely affecting specific hardware / setups. If the developers aren’t able to reproduce it then it’ll probably remain unfixed.

      • sugar_in_your_tea@sh.itjust.works
        2·
        20 hours ago

        Yeah, that’s how bugs tend to go. If they’re hard to reproduce, they tend to get de-prioritized.

        For the record, I’ve had similar issues w/ Chromium bugs, which have been really frustrating in our automated testing pipelines.

        I haven’t run into any significant issues on Firefox (primary platforms are Linux, macOS, and Android), so I stick w/ it.