On Sat, 21 Feb 2009, Pritpal Bedi wrote:
Hi,
> As I posted ( Toninho too ) about memProof.exe' report
> of unfreed memory pages at appln termination,
> here are the investigations.
> I used following debugging code:
> /* For direct MMAP, use MEM_TOP_DOWN to minimize interference */
> static void* win32direct_mmap(size_t size) {
> void* ptr = VirtualAlloc(0, size, MEM_RESERVE|MEM_COMMIT|MEM_TOP_DOWN,
> PAGE_READWRITE);
> OutputDebugString( "--------------------VirtualAllocate win32direct_mmap"
> );
> return (ptr != 0)? ptr: MFAIL;
> }
[...]
Yes, DLMALLOC does not release all allocated memory on application exit.
It's not real problem but it will be nice if it can be eliminated because
it makes harder debugging other code and finding memory leaks.
But 1-st you should check if it's the only one problem. Harbour frees
all allocated memory on application exit so if CRTL also does it then
we can try to add cleanup call to dlmalloc.
So please check what happens when you compile Harbour using
-DHB_FM_WIN_ALLOC
If it pacify all memproof messages then we can try to fight with
DLMALLOC. If not then there is still problem with CRTL of given
compiler and we cannot make too much to fix it.
best regards,
Przemek
_______________________________________________
Harbour mailing list
[email protected]
http://lists.harbour-project.org/mailman/listinfo/harbour
