Slimium: Debloating the Chromium Browser with Feature Subsetting

Re:Slimium: Debloating the Chromium Browser with Feature Sub... by RantyDave on Monday November 09, 2020 @10:36PM (#25042599)

With the exception of reducing the exploitable surface, what is the point of debloating chrome?

Code only gets pulled off disk and into memory, and out of memory and into the cache if it actually gets called yes? So the initialisation code for something like WebUSB would get called as the browser wakes up, but then never called again and the majority of it would never even make it off the disk. Are there really gains to be made here?

[ Parent | on HN ]

Re:Slimium: Debloating the Chromium Browser with Feature Sub... by Rebelgecko on Monday November 09, 2020 @10:43PM (#25042623)

Probably disk space. Saving webUSB once isn't a big deal, but if you have 30 copies of Chromium on your computer it could add up

[ Parent | on HN ]

Re:Slimium: Debloating the Chromium Browser with Feature Sub... by londons_explore on Tuesday November 10, 2020 @10:06AM (#25046747)

Even SSD's have appreciable latency. That means you typically read far more code into RAM than you need to run.

Having said that, the executable size in RAM is tiny compared to the runtime ram usage.

[ Parent | on HN ]