| .. |
|
tlsf
|
2d8d0dd851
fix `@(optimization_mode)` usage in builtin collections
|
hace 1 año |
|
virtual
|
e82a0c8fc7
Fixed crash in arena_free_all() for bootstrapped growing arenas.
|
hace 8 meses |
|
alloc.odin
|
3ed2ab6e2c
[mem]: Adjust the docs for calc_padding_with_header
|
hace 1 año |
|
allocators.odin
|
1cf7a56ba7
General clean up of code
|
hace 8 meses |
|
doc.odin
|
e90f5d2528
[mem]: Adjust the docs on the buddy allocator
|
hace 1 año |
|
mem.odin
|
1cf7a56ba7
General clean up of code
|
hace 8 meses |
|
mutex_allocator.odin
|
1dd9b8560d
build mutex allocator code on freestanding wasm
|
hace 11 meses |
|
raw.odin
|
016d1a84d4
[mem]: Document mutex, rollback stack and tracking allocators
|
hace 1 año |
|
rollback_stack_allocator.odin
|
466e29bb38
[mem]: Rollback allocator API consistency
|
hace 1 año |
|
tracking_allocator.odin
|
e5f32e1455
Makes tracking allocator default to crashing on a bad free instead of add to bad_free_array. The bad_free_array remains to not break old code. The new default behavior is implemented in a callback that you can override, there's a second provided callback that provides the old behavior where an element was added to bad_free_array. Rationale: Many people are just checking the allocation_map, but don't check the bad free array. Several examples throughout core that use tracking allocator don't check bad_free_array either, so people have been taught not to check it.
|
hace 8 meses |
gingerBill
2a29322c91
Merge pull request #4605 from karl-zylinski/tracking-allocator-bad-free-default-to-crash