This Question is Possibly Answered

1 "correct" answer available (4 pts) 2 "helpful" answers available (2 pts)
4 Replies Last post: Feb 24, 2011 1:03 PM by Ivan Shakhov  
Sidharth Mohan Newbie 3 posts since
Feb 17, 2011
Currently Being Moderated

Feb 17, 2011 6:05 PM

Problem in getting a memory snapshot

Hi,

 

   I am using dot Trace 3.5 Memory and when i try to get a snapshot of an application running on .net 4 framework by hitting "Get Snapshot" or "Dump Memory" the profiler just hangs and i can see from the event viewer that the w3wp.exe process crashed.

 

This happens everytime i try to get a memory snapshot. I am using windows 2003 service pack2.

 

Please let me know if any other details are required

 

This is the info i get from the Event Viewer

 

Event Type: Error
Event Source: .NET Runtime
Event Category: None
Event ID: 1023
Date:  2/16/2011
Time:  12:30:45 PM
User:  N/A
Computer: TLPFBRWS
Description:
Application: w3wp.exe
Framework Version: v4.0.30319
Description: The process was terminated due to an internal error in the .NET Runtime at IP 7914EFC9 (79140000) with exit code 80131506.


For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.

 

 

Event Type: Error
Event Source: .NET Runtime 4.0 Error Reporting
Event Category: None
Event ID: 1000
Date:  2/16/2011
Time:  12:30:47 PM
User:  N/A
Computer: TLPFBRWS
Description:
Faulting application w3wp.exe, version 6.0.3790.3959, stamp 45d6968e, faulting module clr.dll, version 4.0.30319.1, stamp 4ba1d9ef, debug? 0, fault address 0x0000efc9.

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
Data:
0000: 41 00 70 00 70 00 6c 00   A.p.p.l.
0008: 69 00 63 00 61 00 74 00   i.c.a.t.
0010: 69 00 6f 00 6e 00 20 00   i.o.n. .
0018: 46 00 61 00 69 00 6c 00   F.a.i.l.
0020: 75 00 72 00 65 00 20 00   u.r.e. .
0028: 20 00 77 00 33 00 77 00    .w.3.w.
0030: 70 00 2e 00 65 00 78 00   p...e.x.
0038: 65 00 20 00 36 00 2e 00   e. .6...
0040: 30 00 2e 00 33 00 37 00   0...3.7.
0048: 39 00 30 00 2e 00 33 00   9.0...3.
0050: 39 00 35 00 39 00 20 00   9.5.9. .
0058: 34 00 35 00 64 00 36 00   4.5.d.6.
0060: 39 00 36 00 38 00 65 00   9.6.8.e.
0068: 20 00 69 00 6e 00 20 00    .i.n. .
0070: 63 00 6c 00 72 00 2e 00   c.l.r...
0078: 64 00 6c 00 6c 00 20 00   d.l.l. .
0080: 34 00 2e 00 30 00 2e 00   4...0...
0088: 33 00 30 00 33 00 31 00   3.0.3.1.
0090: 39 00 2e 00 31 00 20 00   9...1. .
0098: 34 00 62 00 61 00 31 00   4.b.a.1.
00a0: 64 00 39 00 65 00 66 00   d.9.e.f.
00a8: 20 00 66 00 44 00 65 00    .f.D.e.
00b0: 62 00 75 00 67 00 20 00   b.u.g. .
00b8: 30 00 20 00 61 00 74 00   0. .a.t.
00c0: 20 00 6f 00 66 00 66 00    .o.f.f.
00c8: 73 00 65 00 74 00 20 00   s.e.t. .
00d0: 30 00 30 00 30 00 30 00   0.0.0.0.
00d8: 65 00 66 00 63 00 39 00   e.f.c.9.
00e0: 0d 00 0a 00               ....  

Ivan Shakhov JetBrains 95 posts since
Mar 31, 2010
Currently Being Moderated
Feb 22, 2011 3:24 PM in response to: Sidharth Mohan
Re: Problem in getting a memory snapshot

Sorry for the delay.

Do I understand right that you use  windows 2003 SP2 x86?

Does this issue reproduces at other machine? If not, then there might be some problem with dotNetFramework - try to repair it.

 

WRB, Ivan Shakhov

Ivan Shakhov JetBrains 95 posts since
Mar 31, 2010
Currently Being Moderated
Feb 24, 2011 1:03 PM in response to: Sidharth Mohan
Re: Problem in getting a memory snapshot

I have tried to reproduce your setup (Server 2003, IIS, .Net 4.0) and it worked fine for me.

Then I contacted developers, and it looks like you have faced some known dotTrace 3.5 issue.

It could not be fixed in the 3.5 version timeframe, but it will definetly not exist in dotMemory 4.0.

 

WRB, Ivan Shakhov

More Like This

  • Retrieving data ...