Hey Chromium, Dear Firefox. You two realize you're not actually a virtual machine, right?
Could you please stop fighting over who can use the most memory? It's not a contest.
So in the early 90s, SUN had a research project that produced the Self programming language. Self is a Smalltalk dialect/descendant that is prototype-based instead of class-based (i.e. OOP but without classes; objects hold methods directly.)
Self was the testbed for modern JIT research; lots of clever compile-multiple-versions-of-methods stuff. It was fast but consumed a *huge* amount of memory for the time.
@fribbledom It’s not a virtual machine, it’s many different and extremely complicated virtual machines in one, unfortunately.
@fribbledom for goodness sake, you know better than to post nonsense like this.
If you have RAM, the browser will use it. If you're running out of memory, the browser will free it up. That's how garbage collected memory systems and caches and many other technologies *work*.
If for some reason you want the browser to use less memory, run it on a PC with less memory available. I promise you it still works just fine.
Well, yes, I certainly do kinda know what's going on in the background. That doesn't mean this isn't problematic. Along with the kernel, now I have two systems fighting over that resource, both optimistically caching away until it's too late. If what the browsers do worked fine, I wouldn't see them getting OOM-killed by the kernel all that often.