Not a big deal, but currently, when running a game in debug mode, any FlameGame
that is ever started will forever be retained in memory unless replaced with a different FlameGame
.
From FlameGame
's constructor:
if (kDebugMode) {
DevToolsService.initWithGame(this);
}
There is no DevToolsService.detachGame()
or anything similar.
This can be confusing when one's looking at memory (albeit I agree that one should be normally doing that in profile mode) and sees a game that's supposed to be gone a long time ago, and won't go away even after manual GC.
This almost sent me on a wild goose chase for a giant game-sized memory leak.
I'm not sure myself if this is something worth addressing. Just putting this here before I forget.
Pay now to fund the work behind this issue.
Get updates on progress being made.
Maintainer is rewarded once the issue is completed.
You're funding impactful open source efforts
You want to contribute to this effort
You want to get funding like this too