🚀 go-pugleaf

Greetings -
I'm hoping this is the correct place for this memory question.

There has been quite a bit of discussion in the past on how the mem mgr.
holds on to memory and never gives it back to the system previously.

I have a TThread'ed application that in the win2k task manager, shows
increasing peak & virtual memory when this program is placed under heavy
usage.

I have scoured the program w/memproof, etc and eliminated most dynamic
memory calls from my code, but I still have the memory creeping up as
threads are being created, destroyed, etc. The thread count, etc all stays
normal, just memory creeps. It gets to a point where the program fails to
respond, and it has to be killed & restarted.


I have seen other people having similar problems.


Is it possible leaks are occuring in libraries, tthreads, etc, or bugs in
mem mgr not freeing memory?


Just curious if anyone has any good resources or insights on this subject.

Thanks,
Curt


P.S. - The next step is cut bcb out of picture & go for a pure winapi
re-write (yuck)