On Tue, 24 Feb 2009, Przemyslaw Czerpak wrote: Hi, > The only one thing which probably exist in DLMALLOC which > it not pleasure but does not cause any real problems is > the fact that it may not release all memory area allocated > by VirtualAlloc() and always keeps some small block(s) for > performance reasons - DLMALLOC does not know that the > application is exiting so it will not allocate any new > memory block in a while. So keep some peace of memory > to quickly realize such request. It's nothing wrong in > the above though it may cause some false alarms in tools > like memproof so if it will not cost too much we can try > to pacify it.
I've just look at it and I can add cleanup call but it will work only if DLMALLOC is compiled with DL prefix. When it replaces CRTL malloc/free/realloc/calloc/... functions then even if I'll execute cleanup call on HVM close then still CRTL functions executed later in CRTL exit phase may reactivate it or even GPF may appear if some memory was allocated by CRTL at startup then I'll force cleanup in DLMALLOC and on exit the memory will be freed or accessed. So if you want then I add such functionality but it will be enabled only when USE_DL_PREFIX is defined. If you make some test which confirm that the virtual addresses as freed as expected then we can enable USE_DL_PREFIX as default. best regards, Przemek _______________________________________________ Harbour mailing list [email protected] http://lists.harbour-project.org/mailman/listinfo/harbour
