Georgeth47
Programmer
Hi,
I am working on memory leak detection in our DLLs. The DLLs are loaded on Apache server.
At the time of Apache startup, some of the code is executed and as we access the URL, further functionality is invoked. The issue is that the process explorer detects memory leaks (a rise in memory consumption) after the URL's are accessed and the web browser is closed. This may be a correct behavior.
However, in the case of IIS , when we stop IIS, our memory clean up functionality is invoked (we can see it from our logs). I assume that this is because all our DLLs are unloaded properly
However, in case of Apache no memory clean up functionality is executed, when we stop Apache. This we can confirm as no logs are written to our log file at the time we stop Apache. Is it that our DLLs are abruptly closed by Apache? Is there a resolution to the issue?
Regards,
George
I am working on memory leak detection in our DLLs. The DLLs are loaded on Apache server.
At the time of Apache startup, some of the code is executed and as we access the URL, further functionality is invoked. The issue is that the process explorer detects memory leaks (a rise in memory consumption) after the URL's are accessed and the web browser is closed. This may be a correct behavior.
However, in the case of IIS , when we stop IIS, our memory clean up functionality is invoked (we can see it from our logs). I assume that this is because all our DLLs are unloaded properly
However, in case of Apache no memory clean up functionality is executed, when we stop Apache. This we can confirm as no logs are written to our log file at the time we stop Apache. Is it that our DLLs are abruptly closed by Apache? Is there a resolution to the issue?
Regards,
George
