Jarrod Davis

So, there seem to be 15 allocations after `win := SDL_CreateWindow('test', 640, 480, 0);` and immediately calling `SDL_DestroyWindow(win)` there are 4 calls to release memory, thus 11 allocations seem to...

Opening and closing multiple windows using SDL_CreateWindow/SDL_DestroyWindow can cause memory leaks. However, when using SDL_CreateWindowFrom with a window created using the Win32 API, no leaks were observed. It is possible...

> There are some allocations that are only cleaned up in SDL_Quit(), have you checked after calling that? The memory leak detection mechanism in Delphi reports memory leaks at the...

Upon conducting a reevaluation of the existing issue, I can confirm that it persists. I have refined the test code to monitor memory allocations and deallocate any lingering resources. The...

Hi, sorry, just saw this message. interestingly, today I just tried with the build I got from the repo on (12/15/2023), only get 1 dangling allocation. Just doing SDL_Init(SDL_INIT_EVERYTHING) and...

> Great, can you get a call stack for those 88 bytes? I'm using Delphi, 64bit SDL DLL. All I have access to is the call stack memory offsets leading...

Ok, found out that whenever one of these flags are added, you will get the 88 byte leak: `SDL_INIT_JOYSTICK | SDL_INIT_GAMEPAD`.

Ok, understand. I d/l and recompiled with this fix, just so you know... those changes, results in 120 bytes leaking. It looks like (so far) it's just this area, so...

> I'm not sure how those changes would result in 120 bytes leaking. We're doing fewer allocations, not more... ? Yea, that is what I had assumed too. I just...

if you run this code, you can see the leak. ```cpp #include #include #define DEBUG_CRT #define _CRTDBG_MAP_ALLOC #include #include static inline void DebugCrtInit(long break_alloc) { _CrtSetDbgFlag(_CRTDBG_ALLOC_MEM_DF | _CRTDBG_LEAK_CHECK_DF); _CrtSetReportMode(_CRT_ERROR, _CRTDBG_MODE_DEBUG...