SGDK Memory

Start with the matching ELF, selected SDK configuration and the point in the game where memory is tight. Distinguish a capacity problem, fragmented free space, a leaked owner, stale references and corruption before changing sizes. Do not impose a heapless architecture or copy the Lab's allocation sizes.

Account for the right space

Separate static work RAM, heap allocations and stack reservation from VRAM, ROM and the sound CPU's memory. A heap counter is not a total-RAM meter. Compare a consistent post-initialization baseline with busy play, transition overlap and repeated return-to-title cycles. Keep unknown peak stack and temporary allocations visible rather than treating them as zero.