🤍 Appeal to the Browser Goddesses 🤍

Can we please make it a thing where 32GB of RAM isn’t an insufficient amount for day to day web browser usage? Getting an OOM core dump for that reason is inexcusable.

  • Should the Zoom browser app really need 2GB on a single tab when it’s already downscaling a 1080p feed to 320p on an enterprise account?
  • Should Amazon’s website really need 1GB per tab just to view the cart or a ~800Mb for a single simple product page?
  • Please remind me how an MKdocs fully static page with a single 400k image and no datatables or fancy JS somehow require 242Mb?
  • Or perhaps shed some light on the requirement where Google’s main page with a single search form somehow needs ~500Mb

There are no “good reasons” for these inefficiencies. We don’t suddenly have better search fields or compressed jpegs now vs a decade ago with 1/10th of the system resources.

#developer #webdev #linux #browsers #chrome #firefox #ensh11n

  • Johan Halse@ruby.social
    2·
    1 month ago

    @winterschon@bsd.cafe it’s usually not as bad as it looks though, browsers will use ALL THE RAM if it’s available because why not, you know? Better to use the memory and make everything fast rather than just leave it lying around! They’ll adjust their usage downwards if other apps need the memory.

    • rdri@lemmy.world
      3·
      1 month ago

      They’ll adjust their usage downwards if other apps need the memory.

      If it really works that way (which I doubt) then I don’t want my apps to spend resources on constantly monitoring the RAM situation.

    • vrighter@discuss.tchncs.de
      3·
      1 month ago

      no, it doesn’t work that way. The os does that with caching because it can release the memory should another user program ask for it. The browser just takes all of that memory. As far as the system is concerned, that memory is in use, not available.