3 ms·
But why are you using Chrome in the first place - it's a known memory and CPU hog! Doesn't Firefox or other Webkit based browsers support webGL fully?
by webmobdev 6y ago
But why are you using Chrome in the first place - it's a known memory and CPU hog! Doesn't Firefox or other Webkit based browsers support webGL fully?
- stonogo 6y agoI don't understand what "memory and CPU hog" is supposed to mean here. Chrome runs faster than Firefox on every single ARM device I've ever used, and since the parent comment is explicitly about running a web app I would guess that nobody really cares if it takes slightly more resources to deliver good performance.
- webmobdev 6y agoBut the point is that the user isn't getting the expected performance and mentions Chrome specifically. So in this case using more resources on a constrained system is the main issue.
- m-p-3 6y agoFF uses more memory on my system than Chrome now..
- heavyset_go 6y agoYou can use cgroups to limit memory available to Firefox, and systemd-run gives you an easy path to do this.