Closed PatchMixolydic closed 4 years ago
Apparently, this isn't happening anymore? It's possible the bug was somewhere else, but further testing is needed before this issue can be closed.
Reproduced the issue that led me to file this bug (glitched characters on screen), I think it might actually be due to memory corruption? It has the same properties as the (yet unfiled) "Page fault at 0xD0000000" bug in that adding extra printf statements (as an example) makes the issue disappear, which makes me think it's high time to rerewrite memory management
Rendered irrelevant due to b20a811
Either i386's memset clears too much, or the generic memset clears too little. i386's memset has a tendency to overwrite the kernel heap metadata while the generic one does not.