News for hackers. Stuff that matters.

A comment on The Linux kernel's inability to gracefully handle low memory pressure. Parent comment

Re:The Linux kernel's inability to gracefully handle low mem... by bjoli on Tuesday August 06, 2019 @03:03AM (#20622856)
On a low memory computer I had configured FF to not show images unless I alt-clicked them. Together with not using JavaScript this meant using significantly less memory. I suspect browsers still have to have raw bitmaps in memory, which for the 2mb jpegs you are fed everywhere quickly adds up...
[ Parent | on HN ]
Re:The Linux kernel's inability to gracefully handle low mem... by chmod775 on Tuesday August 06, 2019 @03:29AM (#20622987)
They have to be in memory somewhere. They technically don't have to be kept in RAM if they are uploaded to VRAM though.

Assumining RGBA it's just over 8MB for a 1920x1080 image.

[ Parent | on HN ]
Re:The Linux kernel's inability to gracefully handle low mem... by gnode on Tuesday August 06, 2019 @07:29AM (#20624183)
Images could be kept compressed until they are painted. Most GPUs support texture compression, so don't need to keep a bitmap for compositing.
[ Parent | on HN ]
Re:The Linux kernel's inability to gracefully handle low mem... by chmod775 on Tuesday August 06, 2019 @08:26AM (#20624491)
Texture compression is inherently lossy, so it isn't an option.

It's also really dependend on your textures and what you want to do with them, you don't want browser to just go give it their best shot at compressing your company logo.

[ Parent | on HN ]