Hello Przemek Harbour compiled with -DHB_FM_WIN_ALLOC doe snot produce any unreleased Virtual Mem Pages as reported by MemProof.
Plus exiting a thread also releases the memory properly. With dlmalloc.c, a thread was never releasing the memory. You start another thread, keep on initiating other threads, close those modules, Task Manager going on reporting increase in memory. At the appln exit, unfreed virual blocks keep on increasing by the number of threads an appln fires. This also shed light on uhttpd's reported high memory consumption in another thread. Francesco ? Something very serious if dlmalloc is the default for Harbour. Probably easy to fix if someone concentrates onto that. Regards Pritpal Bedi -- View this message in context: http://www.nabble.com/Dlmalloc.c---VirtualAlloc-Free---Test-Results-tp22143106p22168610.html Sent from the Harbour - Dev mailing list archive at Nabble.com. _______________________________________________ Harbour mailing list Harbour@harbour-project.org http://lists.harbour-project.org/mailman/listinfo/harbour
