rpmalloc_heap_free - thread safe? about rpmalloc HOT 1 CLOSED

Sure, you can use rpfree for a block from a first class heap, but you must still make sure that only one thread calls it at any given time (the thread ownership test in the free path will just let any thread directly free from a first class heap) - so for a first class heap rpfree will NOT be thread safe.

The other option would be to promote the heap to be the current heap for a thread by using rpmalloc_heap_thread_set_current in which case it will be assigned to the caller thread and now thread safe. Note that you cannot 'unassign' a heap from a thread in this case.

The main use case for a first class heap is when you have a known lifetime of the heap and can do a single call to rpmalloc_heap_free_all to release all memory used in the heap.

from rpmalloc.