So... The guy who posted the links for deleaker. Thank you. I was albe to fix my memory leaks alone. However. using deleaker I found that most of the leaks are comming from DXUT. This means that my program is not behaving correctly on lost/reset/create device/etc. There are my problems comming from. Gonna check the samples DXSDK is comming with. I think I'm destorying the resources in a wrong callback(if I didn't do it anythwere DXUT whoud popup a leak message).
#include <memory>
#include <iostream>
std::string almost_undetectable_memory_leak = "hello world!";
int main()
{
_CrtDumpMemoryLeaks();
return 0;
}
Detected memory leaks!
Dumping objects ->
{143} normal block at 0x00654E68, 8 bytes long.
Data: < 5 > A0 D1 35 01 00 00 00 00
Object dump complete.
How to avoid these messages, so I can find the real leak? I'm sure these strings are released...
