Re:Dealing with Out-of-Memory Conditions in Rust
by SigmundA on Saturday August 14, 2021 @09:12PM
(#28185375)
A program that can handle an OOM and continue to function normally is more reliable to the user than one that crashes and must be restarted potentially losing work.
Memory allocation can fail, network connections are not reliable , opening a file may fail, writing a file may fail and so on. If your program simply crashed because some operation failed it would only be reliable at crashing.
Re:Dealing with Out-of-Memory Conditions in Rust
by ElectricalUnion on Sunday August 15, 2021 @12:26AM
(#28186266)
> continue to function normally
By definition, you are not functioning normally if you're OOM.
Re:Dealing with Out-of-Memory Conditions in Rust
by SigmundA on Sunday August 15, 2021 @07:38AM
(#28187944)
If you try an operation that causes an OOM by say allocating a large amount of memory as the example given above, then that memory is freed you are now functioning normally again.
If you write a large file to disk filling it to capacity, failing then delete the file, now you have free space again and everything is normal.
My comments were directed at people who are interested in building reliable systems.
If you straight assume it is not possible to build reliable systems, you are missing a lot.