Automatically terminating the Profile Session

[ashish_chilke]

Hi,

We are using demo version of ".NET Memory Profiler 4.0" (msi).

Our system configuration is as below

OS: Windows Server 2003 Standard edition SP2.
Ram : 4 GB
Processor 2.3 Ghz
Free Space in "C:" 10.3 GB

We are running this s/w as "Administrator". We looking to test memory leak for our asp.net website.

We use default settings in the time of installation and while using this s/w we are using default settings, and we are "launching Asp.net using IIS".

Issue: ".NET Memory Profiler 4.0" is "Automatically terminating the Session" within just 1 minute after start.

Please suggest us we are want to test our application using this profiler so that we can get the full version of it.

Thanks in advance,
Ashish

[Andreas Suurkuusk]

In what way is the profiler automatically terminating the session? Does the ASP.NET worker process just terminate, or do you get some kind of message? How much memory is the ASP.NET worker process using then the process terminates? When running under the profiler the memory usage of the profiled process will increase substantially. Is there a possibility that there's an out-of-memory condition in the profiled process? (We try to detect this and show a message, but due to the nature of out-of-memory errors, it's not always possible to do this reliably.)

[ashish_chilke]

Thanks for ur immidate reply..

while new profile, I select the option "Enable professional edition features".
It is showing me following message within 2-3 minutes, when i start a new session.
the memory profiler show up "The process terminate..\n do you want to save ...?" .
when i checked in event viewer , it showing error message: Failed to CoCreate profile.

Thanks
Ashish Chilke

[Andreas Suurkuusk]

Do you get the message "Failed to CoCreate profiler" each time you start profiling your ASP.NET application? This message indicates that the profiler has not been loaded into the IIS worker process at all. Does the message "Waiting for profiled process disappear" after you have started the profiler (and before the process terminates)?

[ashish_chilke]

We solved the issue by increasing the virtual memory.
Thanks for your co-operation.