🚀 go-pugleaf

Chris Buys wrote:

>Unfortunately the work the DLL does eats up memory like there's no tomorrow.
>In the Win2000 TaskManager the memory usage for that process keeps going up
>and after 30 min to 1 hour Win2000 runs out of page memory and throws an
>error.

Does the dll do file io? On my 98 system, when I had set the file
cache size to 0, memory would go away slowly. Apparently 0 is infite
size for the cache. Giving Win _some_ cache fixed that problem. Just a
non-programming thought as to the cause of your symptoms.

>So I want to keep the working set of the memory down to sane levels with the
>SetProcessWorkingSetSize API call.
>
>        if (SetProcessWorkingSetSize(P,1048576,2097152) = false) then

Where did P come from? It's probably not right. GetCurrentProcess()
should work better for P.

In any case, SetProcessWorkingSetSize isn't going to fix your problem.
All it does is limit the amount of real memory you use. Your app can
and will still fill the paging file to overload. (At least, that's
what the help says)

>I've already checked the DLL's code for any possible memory leaks, but could
>not determine any.  Any ideas?

Does your app return objects (that the DLL created) back to the DLL
for deletion (correct)? Or does the app delete them itself
(incorrect).


P.S. Please don't cross-post.