🚀 go-pugleaf

If I understand right, there are actually two problems with Malloc violations.
1. Some people do a Malloc and use memory outside of the Malloc'ed range.
2. Some people expect successive Mallocs to return sequential addresses.
#2 is not true even now if your memory gets at all fragemented.  If the
40 folder bug is fixed, the OSPool should be large enough to hold Malloc
Handles, especially if it returns memory into the OSpool correctly.
Alternately, (since I hope no one is expecting to use beyond what a Malloc
(-1) would return) you could put the headers at the very bottom of the largest
Mallocable segment and that might fix the problems and retain compatibility.
I hope you can now MFree in a different order than Mallocing and have it
work properly (this shouldn't be a problem to fix).
Considering I use RTX often, perhaps the 64 bytes extra may be enough of
a buffer to solve #1.
    Perhaps you should try to do some of these fixes and see if your
compatibility percentage improves.  And list what breaks.  If you get to
98% or more, then perhaps it would be better to go to the fixed Malloc
(with the aforementioned compatibility patches).  I seem to remember that
the Mega roms broke a few things.