Memory leaks caused by ASP (VBScript) scripts

[Jeremy1]

I have been working on a server problem on behalf of a client, and the hosting company has decided that the slowdowns the website experiences periodically are due to "a memory leak somewhere in the code of the website." This website is not using any compiled code, so I don't see how it's even possible for the code to have a memory leak. I just want to make sure that I'm correct before I tear these idiots a new a-hole.

[Josh]

Yes it is... if your DB connections and/or other objects are not properly closed at the end of every page execution, it can cause these objects to remain in memory. Remember... ASP does not have "garbage cleanup" like ASP.NET and even ASP.NET can be subject to these things.

And code does not need to be compiled to be loaded into memory... if you remember Computing 101 then you'll remember that before ANYTHING at all executes on any computer it is loaded into memory and run from there. So if these things are not released from system memory they may not always find their way out.

[Jeremy1]

Right, I know all about closing DB connections. Assuming that everything gets closed properly, there is basically no way for an ASP script to leak memory, right?

[Josh]

Sure there is... Recordset objects, improperly used arrays, loops that dont exit properly, i mean you keep leaning towards "there's no way" but there's plenty, and much of it can't be pointed out without looking at your code.

Another thing to consider... if you're working with a large DB, ASP has a timeout period where if the page doesn't finish processing before that amount of time the server will terminate the process and when that happens everything doesn't always get closed/discarded correctly.

There is any number of things it could be... instead of leaning toward "it cant be" how about either helping us help you by posting code or really really going thru it yourself. No harm or hurt intended. :)

[Jeremy1]

Thanks for the info.