yesterday madExcept helped us locate a buffer overrun in our software.
Very happy about that.
Now I wanted to test our App a bit more with the 'buffer overrun' check active.
The problem is that I am getting EOutOfMemory Exceptions very early, so I can barely test anything.
It is clear that when this check is active a lot more RAM will be consumed. But I do believe I have found a problem.
I created a bare bones test application. It has just one button:
Button 1: Keeps allocating Memory until EOutOfMemory is thrown.
I added this to the dpr file:
- Code: Select all
Since I am running on a 64 bit System this gives my 32 bit test project 4 GB of RAM.
I can verify this is the case, when I hit the button and the madExcept box popups once the EOutOfMemoryException is raised.
Allocated memory is at 3.84 GB.
Now if I enable the buffer overrun test, the EOutOfMemoryException is raised much faster.
Allocated memory is at: 1.90 GB.
So it seems that the custom madExcept Memory Manager is not honoring the IMAGE_FILE_LARGE_ADDRESS_AWARE flag.
Could you please comment on this?