WebUI memory management

[jitzerttok51]

Hello I'm new to writing complex applications using C. I know how memory management works and how malloc and free work in normal C programs.
My question is how are webui_malloc and webui_free different and in what scenarios I should use webui's implementation and when the standard functions?

[AlbertShown]

Sure, the mean goal of webui_malloc() and webui_free() is to track pointers to avoid freeing null or double free that can cause program to crash. Another reason is that those functions are exposed to wrappers (Python, Go, Zig, JS...), so, we should expect miss use of those APIs, safety is mandatory here.

However, those functions are pretty simple, when you call webui_malloc(), it calls the standard malloc(), then it saves the pointer in an array. When you call webui_free(), it will check first if that pointer is in that array, if yes then call free(), if not then do nothing, pretty simple.

When I read the debug of webui, I see many times the wrappers free 0x000000, or free 0xXXXX two times, which means if we didn't have those safe APIs the program will crash.