4 ms·
ahah, yeah surprising considering how Chrome is RAM hungry, 20mb isn't that much of a win. On another end when trying to reproduce the glitch, it was quite hard
by gutechh 2mo ago
ahah, yeah surprising considering how Chrome is RAM hungry, 20mb isn't that much of a win. On another end when trying to reproduce the glitch, it was quite hard! basically invisible on photos and not all icons were affected. So it does work very well. It was kind of our fault to use a jpg for an icon ahah.
- kristianp 2mo agoI assumed Chrome is memory hungry due to the JavaScript VM, but there's probably many optimisations that trade memory for speed. (Unlike this one).