You discovered a bug in the engine, and you are sure that it is not a problem of your code? Just post it in here. Please read the bug posting guidelines first.
Irrlicht Engine version 1.4.2
Microsoft Windows XP Professional Service Pack 2 (Build 2600)
Loaded mesh: ../../media/sydney.md2
Loaded texture: ../../media/sydney.bmp
Detected memory leaks!
Dumping objects ->
{53} normal block at 0x003A5C50, 1 bytes long.
Data: < > 00
Object dump complete.
The program '[4072] 01.HelloWorld.exe: Native' has exited with code 0 (0x0).
valgrind doesn't detect anything (under Linux), and if it's really just one byte that was lost...
Anyway, can your tool also find where the memory was allocated?
I've experienced the 1 byte leak before in my own programs (not using Irr at all)
I'm 99% certain it's actually a bug in the way CRT detects memory leaks, since there are a multitude of ways to create this output with "known good" libs etc. (e.g. with STL strings)
Also, the fact it's unable to trace the location in that output (normally it shows the file+line of the leak) indicates its something internal that it's not accounting for