*** ERROR - Free memory (00D015DC - 00D015E0) corrupted *** | developer.brewmp.com *** ERROR - Free memory (00D015DC - 00D015E0) corrupted *** | developer.brewmp.com

Developer

*** ERROR - Free memory (00D015DC - 00D015E0) corrupted ***

Forums:

*** ERROR - Free memory (00D015DC - 00D015E0) corrupted ***

I get this when I am exiting my game with any heap not deleted. I know exactly what isn't deleted because we're using a memory tracker. However, I have no idea how to find what is causing this error.

It used to be that if I left any objects the emulator would just say that I had memory left over...no big deal...now it dies. It looks like its only an INT worth of space. The last time i had this I was deleting something that was already NULL. Fixing that moved that memory area down by one whole object space....

Does anyone have any ideas what else could be the problem?

As the error message very clearly points out in plain english almost, your application has written to some memory locations where it wasn't supposed to write to. Sounds like a buffer overrun or a misdirected/uninitilaized pointer.

As the error message very clearly points out in plain english almost, your application has written to some memory locations where it wasn't supposed to write to. Sounds like a buffer overrun or a misdirected/uninitilaized pointer.

I realize that. However, the problem seems to persist ONLY when I use IWeb to get a web response. If I remove that call I dont get this problem EVER.

I realize that. However, the problem seems to persist ONLY when I use IWeb to get a web response. If I remove that call I dont get this problem EVER.

That doesn't necessarily mean that that IS the problem. You could still be writing into uncharted memory but in that case the application may not realizing it and thus not throw an error message.
IWEB most likely just makes the problem visible - at least from my experience of bugs liek these. The only thing that can help you there is debugging, debugging, debugging. These sorts of bus that you're having are usually the hardest to catch and you should prepare yourself for some long and frustrating debug sessions.

That doesn't necessarily mean that that IS the problem. You could still be writing into uncharted memory but in that case the application may not realizing it and thus not throw an error message.
IWEB most likely just makes the problem visible - at least from my experience of bugs liek these. The only thing that can help you there is debugging, debugging, debugging. These sorts of bus that you're having are usually the hardest to catch and you should prepare yourself for some long and frustrating debug sessions.