&gt; The idea that apps should intentionally throttle their CPU usage to avoid &quot;slowing down other apps&quot; at the expense of performance is nonsensical. Apps should use all the resources in the machine to get the job done faster and go to sleep faster. The kernel, not userland apps, is responsible for multiplexing the system resources: that&#x27;s literally its job, and only it is in a position to do so properly.<p>Did you knew that there are apps running - like IDEs, servers, games etc which requires a large amount of resources? If you run another resource hungry app it might affect your first app&#x27;s runtime which would end up frozing both. Have you ever used resource hungry apps?<p>&gt; Nothing you&#x27;ve cited has been evidence of a leak. Adding a global garbage collector would do nothing to reduce the (non-)&quot;leaks&quot; you observe.<p>600MB RAM for nothing is leak. Denial is futile.<p>&gt; Enabling those via about:config tweaks and addons slows down your browser. Session and history limits do not affect your browser performance.<p>1. It seems like you don&#x27;t have experience with browsers. Go and try them out instead of denying everything. Do you know what is prefetch at all? Or at least pipelining(cheat: <a href="https:&#x2F;&#x2F;en.wikipedia.org&#x2F;wiki&#x2F;HTTP_pipelining" rel="nofollow">https:&#x2F;&#x2F;en.wikipedia.org&#x2F;wiki&#x2F;HTTP_pipelining</a>)?<p>2. Session and history limits DOES affect browser performance at long runtime. If you limit these, your browser will consume less RAM(+ it&#x27;s easier to find in small history) and if another app wants to use its resources the os will put the memory on the swap then it will come back faster.