http://img32.imageshack.us/img32/4120/w3wpgraph.png
Here's an example image showing w3wp.exe private bytes and Gen 0 Heap
size. They seems related, but if I use ".NET CLR Memory/# Bytes in all
Heaps " it is much lower than private bytes. Can we still say that is
an ASP .Net problem?
Moreover analyzing a crash dump the heap size i obtain is smaller, 200
Mb while the crash dump was 700 mb and private bytes about 600 mb.
Here is also a !dumpheap -stat:
I've done a "!dumpheap -mt 000006427881aaf8" (the System.String entry)
and I've found that the bigger strings are aspx pages. I've a lot of
them on my website (thousands). Maybe w3wp.exe is caching them? How
can i disable this feature?
!gcroot on one of this strings gives the following output:
Does this mean it's orphaned but not collected by the GC?
Here's a "!dumpheap -stat -type Cach":
And a !do and a !gcroot of a CacheEntry:
If you need it, I can also give you the link to the whole dump. I've
been working on it for a week without results!
Thanks in advance,
Carl
Sorry to hear of your problem. The information given isn't enough to give
me any clues to the issue. ASP caching can be configured however doing so
will certainly impact performance. Make sure you run it in a test
environment first before making the change to production.
I'm not sure if you've tried it or not but the Debug Diagnostic Tool
provides some functionality that may help you resolve the problem.
You are more than welcome to post a link to a zipped up copy of the memory
dump but these cases are best geared towards the people who analyze memory
dumps on a daily basis, MS product support.
Configuring ASP Caching in IIS 6:
http://www.microsoft.com/technet/prodtechnol/WindowsServer2003/Library/IIS/a5766228-828e-4e31-a92b-51da7d24d569.mspx?mfr=true
Debug Diagnostic Tool v1.1
http://www.microsoft.com/downloads/details.aspx?FamilyID=28bd5941-c458-46f1-b24d-f60151d875a3&displaylang=en
Microsoft product support numbers:
http://support.microsoft.com/default.aspx?scid=fh;EN-US;PHONENUMBERS
If you are outside the US please see http://support.microsoft.com for
regional support phone numbers.
All the best,
Jeffrey Ingalls
"venom00" wrote:
> .
>
http://blogs.msdn.com/tess/archive/2007/08/09/asp-net-memory-issue-high-memory-usage-in-a-64bit-w3wp-exe-process.aspx
http://support.microsoft.com/?scid=kb%3Ben-us%3B912891&x=15&y=5
The first article is exactly describing my issue, but I'm not sure and
the fix isn't public, I've tried to swtich to .Net 3.5 but things
didn't get any better.
I also tried to disable ASP .Net caching throgh web.config but without
results.
What do you think?
Thanks in advance,
Carl
On 19 Nov, 14:25, Jeffrey Ingalls
<JeffreyInga...@discussions.microsoft.com> wrote:
> Hi,
>
> Sorry to hear of your problem. The information given isn't enough to give
> me any clues to the issue. ASP caching can be configured however doing so
> will certainly impact performance. Make sure you run it in a test
> environment first before making the change to production.
>
> I'm not sure if you've tried it or not but the Debug Diagnostic Tool
> provides some functionality that may help you resolve the problem.
>
> You are more than welcome to post a link to a zipped up copy of the memory
> dump but these cases are best geared towards the people who analyze memory
> dumps on a daily basis, MS product support.
>
> Configuring ASP Caching in IIS 6:http://www.microsoft.com/technet/prodtechnol/WindowsServer2003/Librar...
>
> Debug Diagnostic Tool v1.1http://www.microsoft.com/downloads/details.aspx?FamilyID=28bd5941-c45...
This sounds like a poorly designed application. .NET applications have a
good garbage collector, but its still quite easy to write an application
which grabs memory without releasing it (constantly plugging data into the
application cache is one way).
As a short term measure, you can look at the properties for the application
pool for the application (assuming you can identify the appliction and its
pool), and set it to recycle after its used so much memory. If the
application is well written it will survive the application pool being
recycled, if its poorly written (which it might be given your memory issue)
then this might close any sessions that web-ap has open. Try and see.
--
Brian Cryer
www.cryer.co.uk/brian
If the article is exactly describing your issue then I'd call PSS and ask
for the fix. You don't get billed for a hotfix. :)
Yes, you're right. The article I posted was for classic ASP. Sorry about
that.
Article for ASP.NET caching:
http://www.iis.net/ConfigReference/system.webServer/caching
"venom00" wrote:
> .
>