4 ms·
> The difference between volatile and non-volatile memory is in whether the data is lost when the system loses power. I'm aware. This is a feature for me - I d
by Miraste 4y ago
> The difference between volatile and non-volatile memory is in whether the data is lost when the system loses power.
I'm aware. This is a feature for me - I disable suspend/hibernate/resume functionality. I don't want hiberfile.sys taking up space (irrelevant in this scenario, I guess) and I certainly don't want programs to reopen themselves after a restart, especially if it was a crash. If all storage were nonvolatile, OSes would behave as though resuming from hibernate (S4) all the time.
> that memory will be reclaimed [. . .] when the app is closed.
Again, I'm aware. I'm glad you've never had any sort of crash or freeze that would prevent closing a program, but it does happen.
OSes would need to implement a sort of virtual cold boot to clear the right areas of memory, even after a BSOD or kernel panic. Probably wouldn't be that hard, but it would have to happen.
- thaumasiotes 4y ago> Again, I'm aware. Are you? Because according to your words in this more recent comment, your original comment was meaningless gibberish. > If all storage were nonvolatile, OSes would behave as though resuming from hibernate (S4) all the time. That isn't even possible to do. Thus, obviously, it would not be done.
- Miraste 4y ago> That isn't even possible to do. What? Of course it has to have a first boot sometime, but past that S5 would no longer need to exist.
- wtetzner 4y agoYou could still have a restart "from scratch" feature in the OS. But persistent RAM could potentially mean the power dropping for a few seconds means you don't lose your session.