Outofmemoryexception when saving results

twdi

We are evaluating Memory Profiler 5.2.0.49 and it looks a great tool which could help us to increase quality.

Last night I kept the profiler running on our windows Service to check if our application leaks when it runs for a longer periode of time but when I tried to save the results, we've got an exception error:


Event Type: Error
Event Source: .NET Runtime 2.0 Error Reporting
Event Category: None
Event ID: 5000
Date: 30-7-2010
Time: 8:28:26
User: N/A
Computer: computername
Description:
EventType clr20r3, P1 redgate.memoryprofiler.ui.exe, P2 5.2.0.49, P3 4b5490a9, P4 mscorlib, P5 2.0.0.0, P6 4a7cd8f7, P7 35df, P8 45, P9 system.outofmemoryexception, P10 NIL.

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
Data:
0000: 63 00 6c 00 72 00 32 00 c.l.r.2.
0008: 30 00 72 00 33 00 2c 00 0.r.3.,.
0010: 20 00 72 00 65 00 64 00 .r.e.d.
0018: 67 00 61 00 74 00 65 00 g.a.t.e.
0020: 2e 00 6d 00 65 00 6d 00 ..m.e.m.
0028: 6f 00 72 00 79 00 70 00 o.r.y.p.
0030: 72 00 6f 00 66 00 69 00 r.o.f.i.
0038: 6c 00 65 00 72 00 2e 00 l.e.r...
0040: 75 00 69 00 2e 00 65 00 u.i...e.
0048: 78 00 65 00 2c 00 20 00 x.e.,. .
0050: 35 00 2e 00 32 00 2e 00 5...2...
0058: 30 00 2e 00 34 00 39 00 0...4.9.
0060: 2c 00 20 00 34 00 62 00 ,. .4.b.
0068: 35 00 34 00 39 00 30 00 5.4.9.0.
0070: 61 00 39 00 2c 00 20 00 a.9.,. .
0078: 6d 00 73 00 63 00 6f 00 m.s.c.o.
0080: 72 00 6c 00 69 00 62 00 r.l.i.b.
0088: 2c 00 20 00 32 00 2e 00 ,. .2...
0090: 30 00 2e 00 30 00 2e 00 0...0...
0098: 30 00 2c 00 20 00 34 00 0.,. .4.
00a0: 61 00 37 00 63 00 64 00 a.7.c.d.
00a8: 38 00 66 00 37 00 2c 00 8.f.7.,.
00b0: 20 00 33 00 35 00 64 00 .3.5.d.
00b8: 66 00 2c 00 20 00 34 00 f.,. .4.
00c0: 35 00 2c 00 20 00 73 00 5.,. .s.
00c8: 79 00 73 00 74 00 65 00 y.s.t.e.
00d0: 6d 00 2e 00 6f 00 75 00 m...o.u.
00d8: 74 00 6f 00 66 00 6d 00 t.o.f.m.
00e0: 65 00 6d 00 6f 00 72 00 e.m.o.r.
00e8: 79 00 65 00 78 00 63 00 y.e.x.c.
00f0: 65 00 70 00 74 00 69 00 e.p.t.i.
00f8: 6f 00 6e 00 20 00 4e 00 o.n. .N.
0100: 49 00 4c 00 0d 00 0a 00 I.L.....


OS: Windows XP SP3

Could this be a known problem?

nick.maidment

The profiler does take up considerable resources, and more for longer periods of time. Generally speaking you may be able to reduce the number of performance counters for slightly less of a performance hit. How much memory are you running on your XP machine?

twdi

I'm running XP sp3 on a 2Ghz intel Duocore 6400 with 3Gb of ram with a pagefile of max 4Gb.

The C-drive where I save the files has 118Gb free space.

The crash only occures when I use the "Save Profiler Results" option from the File menu. Today It crashed again. Th profiling session was started last friday afternon so it ran over the weekend.

Andrew H

One thing that might be worth trying is unsetting the baseline snapshot before saving: the profiler requires much less memory if it's not performing a comparison.

Reducing the number of performance counters that are being recorded may help with very long sessions as well.