Allocated memory and created objects are supposed to be deallocated and
destroyed when the page script completes. There have been problems in the
past with some of the ADO objects not being destroyed and causing memory
leaks (other com objects may have similar problems) but I don't know of any
problems with arrays.
Make sure that you are closing all ADO objects and setting to all objects to
Nothing as soon as you are done with them. It wouldn't hurt to erase your
arrays but I don't think you would see any impact from that unless your
arrays are very large and a there is a significant delay between the time
that you no longer need the array data and when the page completes.
Just how big are the arrays? Could you process the data in smaller chunks?
--
--Mark Schupp
"Alan Howard" <Xa***********@Xparadise.net.nzX> wrote in message
news:%2****************@TK2MSFTNGP15.phx.gbl...
I think we all know what best practices we should be following - I guess
I'm
wondering if anyone has run up against this sort of situation in the past
and knows whether explicitly erasing arrays makes a difference. I'm not
talking about ADO objects.
"Tim" <th**@ltons.freeserve.co.uk> wrote in message
news:dm**********@news6.svr.pol.co.uk... ...asp tidying up after itself?
...pages going "out of scope"
your not from an M$ background are you!
tidy up everything. leave nothing open.
.close
set=nothing
everything you can!!!
there is no garbage collection in ASP.
pages don't go out of scope when they are closed. the user may close
their
browser, but the server doesn't know this.
hope this gives u some clues.
"Alan Howard" <Xa***********@Xparadise.net.nzX> wrote in message
news:uN**************@TK2MSFTNGP09.phx.gbl... > We're getting "ERROR (0x8007000E) Not enough storage is available to
> complete this operation" errors on a fairly large, busy ASP/SQL Server web > site. The error is being thrown on a line calling oRs.GetRows() on one of > our busiest pages. The array returned from the GetRows() call will be
> 'cleaned up' when the page goes out of scope, but I wonder if we should be > calling Erase specifically after the last usage to explicitly free
> allocated
> memory. Is there any actual benefit doing this cleanup explicitly? I've
> always throught that ASP's memory deallocation was a bit spotty - can
> anyone
> comment.
>
> Thanks.
>
>