CookiePLMonster
commented
4 months ago Would this idea accomplish much? There are many services running on the device at any point and FreeRTOS employs dynamic allocation, so if you used the result of such a function to plan your allocations, you could run into a race where the block(s) were free when you checked, but they stopped being free when you are allocating.
Sounds like it'd be better to guarantee that a failed malloc is "safe" and returns null instead of freezing/crashing.
noproto
DrZlo13
skotopes
Description of the feature you're suggesting.
Currently there's no way to check all of the available heap blocks of memory via the API.
It's not possible to plan heap allocation without repeatedly reserving memory and checking the next largest block with memmgr_heap_get_max_free_block (and if there's insufficient memory rolling back all of the allocations and re-allocating).
The only way I can see (which is a hack) is by setting up a log handler with furi_log_add_handler, call memmgr_heap_printf_free_blocks to dump the free blocks to the log buffered output stream, read back the log and parse each line, then use that in any heap memory planning function.
It would be very helpful to expose a function which can be used to plan help allocation/memory management in FAPs. If the largest sized block isn't checked, any malloc can fail freezing the device.
Anything else?
No response