Merge pull request #133 from mexus/patch-1

OOM behaviour in `vec-alloc.md`
pull/134/head
Alexis Beingessner 6 years ago committed by GitHub
commit 0a8c3a4a4c
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23

@ -37,8 +37,8 @@ that, we'll need to use the rest of the heap APIs. These basically allow us to
talk directly to Rust's allocator (jemalloc by default). talk directly to Rust's allocator (jemalloc by default).
We'll also need a way to handle out-of-memory (OOM) conditions. The standard We'll also need a way to handle out-of-memory (OOM) conditions. The standard
library calls `std::alloc::oom()`, which in turn calls the the `oom` langitem. library calls `std::alloc::oom()`, which in turn calls the the `oom` langitem,
By default this just aborts the program by executing an illegal cpu instruction. which aborts the program in a platform-specific manner.
The reason we abort and don't panic is because unwinding can cause allocations The reason we abort and don't panic is because unwinding can cause allocations
to happen, and that seems like a bad thing to do when your allocator just came to happen, and that seems like a bad thing to do when your allocator just came
back with "hey I don't have any more memory". back with "hey I don't have any more memory".

Loading…
Cancel
Save