They seem to be part of a driver
I get these leak reports only with 64-bit not with 32-bit
How can i hide these messages?
Maybe one of them will work for you? If leaks are in 3rd party code, usually the callstack based HideLeak() API is the best way to hide leaks. But it works only if the callstack clearly points to the 3rd party code. If it doesn't, you may be out of luck, sadly. Of course you can always try to ask the 3rd party provider to fix their leaks.
HideLeak ( 'hasp_unit' );
HideLeak ( 'AddKernelHandle' );
HideLeak ( 'AddHandle' );
HideLeak ( 'AddMemAlloc' );
I have calm. But I would ignore these leaks in the whole project.
From the MBR it is not possible to see where exactly the problem is?
Code: Select all
allocation number: 16514289 program up time: 19,74 s type: InitializeCriticalSection address: $c5ff700 access rights: read/write thread $51d4: 671ee52b madExcept64.dll madExceptDbg 1509 AddHandle 671f80db madExcept64.dll madExceptDbg 4585 InitializeCriticalSectionCallback allocation number: 16514256 program up time: 19,74 s type: HeapAlloc address: $c5f25e0 size: 1056 access rights: read/write thread $51d4: 671ee4c4 madExcept64.dll madExceptDbg 1501 AddMemAlloc 671f0233 madExcept64.dll madExceptDbg 2325 HeapAllocCallback