|
Dear All Ok, this has been bugging us for years and as yet we have
had no successful resolution, so I submit it to your considerable collective
experience: We have an ASP application talking to COM dlls. The dlls are your average
ActiveX COM dlls and are instantiated on the web
server (i.e. no middle tier I am afraid). After an indeterminate amount of
time, a web server just dies (well, it starts collecting connections and stops
responding). We have noticed that over time, private bytes
for DLLHOST goes up and available Mbytes goes down (so, we immediately
think “memory leak”). When available Mbytes gets approx 70-90 Mb
the server goes into spaz-mode and we have to
sacrifice it to save the rest of the farm. This problem is affectionately known
as “the big bug”. You may ask what this has to do with So, finally, my question is: Can anyone recommend some good
tools (I don’t mind paying for them) that will allow us to debug a memory
hole on web servers? Preferably not memproof
because it refuses to work on our servers, but if you have managed to track
down a memory leak on a web server with memprrof, I
would love to hear from you. Thank you Stephen |
