Chi-Kuan Chiu

Update: I've added a second diagram showing node count accumulation with `dynamap` disabled . Also clarified that the test was conducted on a Raspberry Pi 400.

> So, I pushed a changed in box64 to not populate this rbtree unless needed. That means the 1st time a signal appears on a new address, the old way...

Also, as a next step, I'm planning to build a memory profiling tool for Box64, specifically focused on `rbtree` usage. To do so, I’d like to confirm the intended usage...

@ptitSeb Here are the statistics on node creation and usage after commit [91848ef](https://github.com/ptitSeb/box64/commit/91848efa34e1191a7500b98948c4be26b1df0208).  In my case, the number of nodes in `dynamap` is zero, resulting in nearly 90% memory...

That fixed the problem, thanks! Maybe I can list all the required libraries for RV64, similar to how it's done in [X64WINE.md](https://github.com/ptitSeb/box64/blob/main/docs/X64WINE.md) and also steam, since I couldn't find any...

Thanks for the note about `first` —already fixed it. Actually, the reason I wrote this document is because the naming and structure in `custommem.c` felt a bit chaotic at first....

Thanks a lot for the detailed explanation! If you have time, feel free to list any other tricky parts or important areas that you think should also be documented —...

### Allocator The custom memory system in box64 provides three distinct allocators, all sharing the same underlying data structures. - `map128_customMalloc`: A simple bitmap-based allocator that allocates fixed 128-byte slices...

@ptitSeb , Here are the second and third parts of the document. Also, is the main difference between `AllocDynarecMap()` and `internal_customMalloc()` that `AllocDynarecMap()` is designed for single-threaded use, since it...

OK, I will update the document since some of the structure has changed.