RAM Footprint about microui HOT 7 OPEN

Not only SDL but there are GL calls here and there in the demo program.
If you closely see, the demo program first initializes SDL which allocates some space on the heap. Then moving on there's SDL_CreateWindow(...), SDL_GL_CreateContext(...), and some GL functions which individually allocates several amount of space. and they never get free'd by the program itself. Although the kernel will free the space automatically, there can be a situation where allocated space may swap out.

I'm unsure about Windows internals and the meaning of private bytes. If it means dynamic memory, ProcessHacker perhaps also reports leaked memory that the demo program creates.

I've patched the memory leak issues with SDL, and one other. It does satisfy sanitizer but valgrind still complains about memory leaks. Currently don't have enough time, but a deep look will reveal it. Here's the patch file: https://pastebin.com/SWUMNJ6q

from microui.