I'm currently typing this on a 2008 MacBook Pro with a 2.5GHZ Core 2 Duo and 6GB RAM. It's playing a 1080P video on a second monitor and has 5 browser tabs open in two browsers. Currently using 4.7GB RAM and 60% CPU.
Someone using Chrome + Facebook or even a dev writing e.g. Python in VS Code to run locally is probably less likely to hit that.
All day I run Chrome with 3 profiles (as many as 5) and 40+ total tabs (sometimes a much higher number), VS Code, SourceTree, 8 docker containers running various services for dev (7 native, one emulated x86_64), iTerm, Photoshop CC and XD CC.
I run everything I can in the browser including Slack, GMail, GCal, our PM tool, etc.
With all of that said, I don't even know what a "OOM" looks like. The only real performance issues I have deal with an inherited codebase (which does stuff it really shouldn't be doing) and docker-specific filesystem slowness (which is a known issue).
OOM on Linux looks like the OS just killing the heaviest application if you have no swap, or grinding to a halt if you have swap and actually need to use it as working memory.
OOM on Windows looks like your system grinding to a halt because you're paging all the time.
It sounds like your use case requires more than the baseline. You may be the outlier.