Rockbox

Your player doesn’t have an MMU, so memory returned by free() is often lost due to fragmentation. This is a memory leak, but one caused by a hardware limitation of trying to use malloc on a device without an MMU.

Hi. Michael. If you go to plugins, games, doom.rock, the top option is “Game”. If you select that, there are two or three other confusing options: Freedoom (the default which if selected gives a memory leak), “Doom Shareware,” and “doom 2.” Doom shareware is only a few levels inside a single wad file. The game begins with you looking at a dead monster on a pool of water. There is a menu to two other games inside, but since this is the shareware version, they don’t work. This version doesn’t work with addons, so it is limited in that you can’t download new wads, unless you rename files. I don’t know which files to rename yet. If you know please tell me.

Anyway, to get to my point, as you may not be aware of this, there are zero problems with the “Doom Shareware” game. You can save and load it all day long without any problems. This is with the same exact same hardware.

Therefore, with all respect that might be due to your comment, you are definitely wrong that this leak is caused by a hardware issue that cannot be fixed.

It can be fixed, just rewrite the function to not expect an MMU. Anyway, this is a long known issue with doom, so it’s not necessary to report.