ASP.NET Memory Leak - OracleConnection/OracleCommand

0
votes

I have followed the advice in the following tutorial: http://humblecoder.co.uk/tag/windbg. I have got to he point that says, run this command: !dumpheap. I have added he total number of bytes in the third column and divided it by 1024 and 1024 again. This equates to 42MB. The ASP.NET process in question is over 1.5GB in size.

This is done on a Windows 2003 server were there is no option to create a dump file in Task Manager. Therefore I have to run the following cmmand: .dump /ma w3wpdump.dmp. As this is a mini dump, is there stuff that is missing that could help?

I did ask another question about this yesterday, which outlines the problem: ASP.NET Memory Leak - OracleCommand Object

1
asp.netwindbg

1 Answers

0
votes

Looking at your other question is appears that the vast majority of your memory usage is being used by strings. I would dump some of those strings to see what is inside of them. You can view the contents of the string using dd or db or du and giving it the memory address of one of the instances of the strings. i.e. dd 0x12345678 and it will dump the raw contents of the memory located there. You can look at the windbg help to get more information on the d* commands.

But if you're sure the managed heap doesn't appear to be consuming the memory then I would look at the unmanaged heap. !heap -s will give you a summary of the unmanaged heaps, which might be where you have excess memory usage.