Ichthyostega
2cd51fa714
...causing the system to freeze due to excess memory allocation. Fortunately it turned out this was not an error in the Scheduler core or memory manager, but rather a sloppiness in the test scaffolding. However, this incident highlights that the memory manager lacks some sanity checks to prevent outright nonsensical allocation requests. Moreover it became clear again that the allocation happens ''already before'' entering the Scheduler — and thus the existing sanity check comes too late. Now I've used the same reasoning also for additional checks in the allocator, limiting the Epoch increment to 3000 and the total memory allocation to 8GiB Talking of Gibitbytes... indeed we could use a shorthand notation for that purpose... |
||
|---|---|---|
| .. | ||
| mock-elm.hpp | ||
| placeholder-command.hpp | ||
| test-element-access.hpp | ||
| test-nexus.cpp | ||
| test-nexus.hpp | ||