Hi



What does xspwp.exe file do? It's sometimes taking about 350 Mb of memory.

Am I doing something wrong?



Rami



--

rami@l...

That's the ASP.NET worker process. This is where the managed code and CLR 

execute. There a known memory leak here, that happens every time an app is 

reset. Scott Guthrie actually mentioned this when he formally announce the 

release of the Beta 1 on thsi list. here's what he wrote (the original 

message is here: http://p2p.wrox.com/archive/aspx/2000-11/22.asp):



> Known Bugs:

>

> Although we fixed just about every bug we knew about with Beta1 -- there

> was one that we were unable to "safely fix" in the Beta1 timeframe.  This

> is the application unloading bug that also existed in the PDC release, and

> results in a memory leak every time a web application is reset (ie: a file

> is changed in the "bin" directory, global.asax is updated, or a config

> file is modified on a running application).  Note that this bug does not

> effect running applications in production (you only run into it when

> actively making changes to an application). 

>

> We have just checked in the fix to the Beta2 tree -- however, we deemed

> the resolution too big a change to attempt for beta1 (we want a few weeks

> coverage on it before we declared it fully resolved).  As a result, for

> Beta1 you will probably see the memory usage of the xspwp.exe process

> being higher than expected as a result.  Note that the ASP.NET process

> model in Beta1 will automatically detect and recover from this leak once

> the process grows beyond 40% of the total virtual memory size of the

> system -- so hopefully most users will remain somewhat oblivious to the

> issue.  However, I just wanted to give people a heads up in case you were

> wondering why the product seemed a bit memory hungry.



HTH

Daniel walker

wrox Press



> 

> Hi

> 

> What does xspwp.exe file do? It's sometimes taking about 350 Mb of memory.

> Am I doing something wrong?

> 

> Rami

> 

> --

> rami@l...