A suspected YouTube interface bug  spikes RAM usage above 7 gigabytes, users report severe lag and frozen tabs — bug might be trapping browsers in an endless layout loop

Comments

• Enkers@sh.itjust.works ⁨1⁩ ⁨week⁩ ago

  Lemme guess: it works perfectly fine in chrome. Google has been using this sort of anticompetitive tactic for years to wage war against other browsers.

  source

  • Alexstarfire@lemmy.world ⁨1⁩ ⁨week⁩ ago

    Yes. I regularly have to either close Firefox or kill the GPU process in it so it’ll free up RAM. Worst I saw it was at 13GB.

    source
  • Chozo@fedia.io ⁨1⁩ ⁨week⁩ ago

    Unpopular opinion: If it works in the engine that 70+% of devices are using, then it works. If it doesn't work in your non-Chrome browser, then your browser is what's broken.

    source

    • Zerot@fedia.io ⁨1⁩ ⁨week⁩ ago

      Except that it has been found in the past that Google/YouTube has been serving different html to Firefox than to Chrome. If they would be serving the same html, then you might have a point. But even then, Google can push through non standard changes to both chrome and YouTube before Firefox even has had a chance of making it compatible.

      source

      • -> View More Comments
    • Goun@lemmy.ml ⁨1⁩ ⁨week⁩ ago

      You’d be rooting for ie6 some years ago. Indeed an unpopular opinion.

      source
    • Goodlucksil@lemmy.dbzer0.com ⁨1⁩ ⁨week⁩ ago

      The problem here is that antitrust does not work correctly and google hasn’t been legally forced out of the industry due to anticompetitive tactics

      source
    • DacoTaco@lemmy.world ⁨1⁩ ⁨week⁩ ago

      Not also unpopular, but also wrong.
      Often times firefox is following the css specifications in how to process it and chrome isnt. Developers then do things, see it works in chrome and leave at that, not knowing what they did is wrong and broken.

      On top of that logic of yours, ie10 was like the perfect browser and everyone should have kept making stuff compatible with it

      source
    • lime@feddit.nu ⁨1⁩ ⁨week⁩ ago

      that would be a more relevant opinion if google hadn’t made itself head of the web standards committee and is changing things so fast that the only party able to keep up is google.

      source
    • Hupf@feddit.org ⁨1⁩ ⁨week⁩ ago

      Keep the faith

      source
    • AHemlocksLie@lemmy.zip ⁨1⁩ ⁨week⁩ ago

      Turns out that’s not how standards work. If all browsers implement the standard and your product doesn’t function properly on every single one of them, the problem is your product, even if it’s just a single one.

      source