Is it really so hard not to crash when running out of memory?

That's a rather arrogant question if I am part of the problem by abusing tabs in the hundreds instead of a browser history or something better (6 gigs, 600 tabs, so ca. 10MB per tab), no swap space, and lots of tabs in private mode for no other reason than that the window was already open (and even if not, form content is not always rescued). Apparently Fx tree-style-tabs is buggy, too (kernel.log implicates Chrome_ChildThr plugin-container), but the same thing happens with chromium even sooner if JS is turned on. I just never close tabs, never go back to them. A prompt that now is the last chance to organize the tabs or loose all would be really helpful. I'm really frustrated right now. There must be a good reason not to focus on this corner case. I mean I was watching a youtube video filling the space. A completely predictable dead end and now I have to feel blamable because I didn't keep eye on the free RAM?

I have no illusion that servo/rust will be any help either, if the UI is written in javascript.