3 ms·

Doesn't sound to me like it's an inherent problem to the browsers, but rather that you'd just need to troubleshoot what's causing the RAM usage. I have no idea

by Sylos 10y ago

Doesn't sound to me like it's an inherent problem to the browsers, but rather that you'd just need to troubleshoot what's causing the RAM usage. I have no idea about Chrome, but in Firefox you can get a detailed breakdown of what's using RAM by typing "about:memory" into the URL-bar and hitting enter. Then click on the "Measure"-button to the left. There's also a few buttons on that page to enforce a memory clean-up, so maybe you can try those instead of restarting Firefox next time, if you can't find a solution. Usually, memory usage like that is caused by some faulty extension, so that's what you should look out for. You could also try, if it doesn't happen anymore in a fresh profile: https://support.mozilla.org/en-US/kb/profile-manager-create-and-remove-firefox-profiles https://support.mozilla.org/en-US/kb/profile-manager-create-...

talos 10y ago
I didn't take a screenshot yesterday when I posted this, but when I've looked in the past most of the memory seems to have piled into "js-non-window". Actually, checking now -- having left one tab, with only this HN thread left open overnight (and computer closed) FF's memory usage has crawled back up to 2.88GB. In "Explicit Allocations", 488MB of that are "heap-overhead". 455MB go to js-non-window" , of which 254MB are "zones" and 183MB "runtime". "window-objects" take 279MB, (the js-compartment for about:blank takes 151MB). Another 259MB for "heap-unclassified", and 155MB for "gfx". In "Other measurements", there are 745MB of "decommitted", of which almost all is "js-non-window". "js-main-runtime" is 666MB, split evenly between "compartemnts" and "runtime" or "zones". Nothing else is of much significance. No extensions or plugins seems are explicitly noted in the memory breakdown. In my experience GC, CC, and Minimize Memory Usage make no difference. I do make use of Noscript and Privacy Badger, and I suppose I should try disabling them -- but my gut says disabling plugins that block scripts won't reduce JS memory usage. Pretty much every time I've checked it really looks like oodles of JS-related memory leakage. Anyway, not expecting a diagnosis here -- this isn't the appropriate forum for that. Just venting a bit. Thank you for your suggestions!
- bzbarsky 10y ago
  js-non-window basically means "extensions and the browser UI itself".

by Sylos 10y ago

talos 10y ago

I didn't take a screenshot yesterday when I posted this, but when I've looked in the past most of the memory seems to have piled into "js-non-window". Actually, checking now -- having left one tab, with only this HN thread left open overnight (and computer closed) FF's memory usage has crawled back up to 2.88GB. In "Explicit Allocations", 488MB of that are "heap-overhead". 455MB go to js-non-window" , of which 254MB are "zones" and 183MB "runtime". "window-objects" take 279MB, (the js-compartment for about:blank takes 151MB). Another 259MB for "heap-unclassified", and 155MB for "gfx". In "Other measurements", there are 745MB of "decommitted", of which almost all is "js-non-window". "js-main-runtime" is 666MB, split evenly between "compartemnts" and "runtime" or "zones". Nothing else is of much significance. No extensions or plugins seems are explicitly noted in the memory breakdown. In my experience GC, CC, and Minimize Memory Usage make no difference. I do make use of Noscript and Privacy Badger, and I suppose I should try disabling them -- but my gut says disabling plugins that block scripts won't reduce JS memory usage. Pretty much every time I've checked it really looks like oodles of JS-related memory leakage. Anyway, not expecting a diagnosis here -- this isn't the appropriate forum for that. Just venting a bit. Thank you for your suggestions!

bzbarsky 10y ago
js-non-window basically means "extensions and the browser UI itself".