dllhost.exe memory size

[Khaled Omar]

I am running a web application with application protection
level set to high, so it runs in a separate dllhost.exe
process, the process takes around 14,000 K of memory I
wanna know if this is fine or I have a memory leak problem

I set all record sets to nothing without closing them and
also I close the database connection

Are there any tools that can measure the ASP page
performance and tell me where do I have performance
bottlenecks ?

Thank You

[Aaron Bertrand [MVP]]

> process, the process takes around 14,000 K of memory I

wanna know if this is fine or I have a memory leak problem
14 MB doesn't sound like a big problem at all. Is it constantly growing, or
does it stay stable?
I set all record sets to nothing without closing them and
also I close the database connection

Do you have a reason for this, other than laziness?

ALWAYS close all objects, and ALWAYS set them to nothing. Unless an object
doesn't have a close method (e.g. FileSystemObjec t), there is no plausible
reason to only set it to nothing. There is also never a good reason to just
"not bother" setting an object to nothing. ALWAYS destroy what you create.

--
Aaron Bertrand
SQL Server MVP
http://www.aspfaq.com/

[Khaled Omar]

It increases when we use the application and browse more
pages which is normal, it reached 25 MB, when should I get
worried, one other thing, the memory allocation doesn't go
down when I close the browser, when should that happen ?

Thanks

-----Original Message-----

process, the process takes around 14,000 K of memory I
wanna know if this is fine or I have a memory leak problem

14 MB doesn't sound like a big problem at all. Is it constantly growing, ordoes it stay stable?

I set all record sets to nothing without closing them

and also I close the database connection

Do you have a reason for this, other than laziness?

ALWAYS close all objects, and ALWAYS set them to

nothing. Unless an objectdoesn't have a close method (e.g. FileSystemObjec t), there is no plausiblereason to only set it to nothing. There is also never a good reason to just"not bother" setting an object to nothing. ALWAYS destroy what you create.
--
Aaron Bertrand
SQL Server MVP
http://www.aspfaq.com/
.

[Aaron Bertrand [MVP]]

> worried, one other thing, the memory allocation doesn't go

down when I close the browser, when should that happen ?

When the session goes out of scope, probably. You will probably relieve
some of this by using CLOSE + SET TO NOTHING for both recordsets and
connections.

Also, see http://www.aspfaq.com/2424 for other ideas on general efficiency,
and a few on reducing memory footprint of ASP pages.

--
Aaron Bertrand
SQL Server MVP
http://www.aspfaq.com/

[J. Baute]

"Khaled Omar" <ko**@hotmail.c om> wrote in message
news:d1******** *************** *****@phx.gbl.. .

It increases when we use the application and browse more
pages which is normal, it reached 25 MB, when should I get
worried, one other thing, the memory allocation doesn't go
down when I close the browser, when should that happen ?

If you are worried about memory leaks just keep an eye on the memory ussage
of your application while you run through it. Opening new pages ussually
will make the app allocate some more memory, refreshing the same page
however shouldn't, or shouldn't take as much as it did initially.
When you keep refreshing a page, and you see the memory rise with the same
amount with every refresh, chances are you have a memory leak in that page.