Windows and free memory management?

Question

Windows

good afternoon. Faced on Windows with such an interesting moment. if you turn off the paging file and open browsers, games, etc., then Windows starts to swear in events, and then something will definitely fall with an error 0xe0000008 or 0x80000003.
I, in turn, remembered that on the 1607 build this was not even with the paging file disabled. cursed at the exhaustion of memory by an error on the desktop, but nothing fell ...
such a question - how should it behave then? You never know if it really should fall with an error and 1607 was it the wrong build?
(maybe it's just "buggy" for me, but I remember exactly that the same firefox with "memory leaks" through all sorts of garbage widgets could eat up to 12 out of 16 gigabytes, everything could freeze but nothing fell for sure)

Answer 1

if you disable the paging file and open browsers, games, etc., then Windows starts to swear in events, and then something will definitely fall with an error 0xe0000008 or 0x80000003

Amazing, isn't it? Who would have thought?
Some kind of OOM-killer works, they did the right thing by introducing it.

Answer 2

then Windows starts swearing in events, and then something will definitely fall

Of course, this is how it should be.

I, in turn, remembered that this was not on the 1607 build

There wasn’t, there wasn’t a lot of things before, and they rode mostly on horseback, now everything is a little different.

such a question - how should it behave then?

If the application does not have enough memory, it should fall - there is no other way.

Answer 3

No you, not buggy. But it was not in the top ten, in XP - without a service pack. With the 1st service pack, the algorithm for working with virtual memory has fundamentally changed there, and such things have begun.
And in the top ten, on a new computer and with an SSD - the best option is not to touch anything at all.