.NET Debugging Demos Lab 6: Memory Leak - Review

re: .NET Debugging Demos Lab 6: Memory Leak - Review

bretttabke — Mon, 17 Mar 2008 13:42:06 GMT

About MSN (Live), the big mistake sitemap.xml

Sitemap 0.90 in the Microsoft support at the same time, Microsoft has put a big mistake, unable to submit such as:

Www.example_example.com

Www.example-example.com,

Www.example.com and www.example.example.com only to the website, such as the example-example.com I will always be “The web address isn’t valid.” Block from the webmaster.live.com the.

re: .NET Debugging Demos Lab 6: Memory Leak - Review

Tess — Mon, 17 Mar 2008 14:05:24 GMT

not sure i follow...

re: .NET Debugging Demos Lab 6: Memory Leak - Review

Christopher Lewis — Tue, 18 Mar 2008 19:41:05 GMT

Tess -

How did you think to look at Assemblies in PerfMon? Do you have a set of PerfMon counters that you *always* typically look at for memory leaks?

For our ASP.NET sites, we are periodically dumping the following:

.Net CLR Exceptions(*)

.Net CLR Memory(*)

ASP.Net Apps v2.0.50727(*)

ASP.Net v2.0.50727\Worker Process Restarts

Memory\Available Bytes

Would you recommend always dumping .Net CLR Assembly stats also?

re: .NET Debugging Demos Lab 6: Memory Leak - Review

Tess — Wed, 19 Mar 2008 00:30:01 GMT

if it is a memory leak or increasing memory usage and I can rule out .net objects the option is either a native memory leak or a .net loader memory leak.

When I have ruled out managed memory as the highest bidder I look at the assemblies, it is a pretty quick check and it saves me from doing leaktracking with debugdiag but debug diag would also have shown the same thing, i.e. that most of the allocations were on the .net loader heap.

Since .net loader heaps are fairly frequent i usually include all .net counters in the perfmon logs (including .net clr loading). They don't contain too many data points so there is minimal or no impact on the system to listen for them.

re: .NET Debugging Demos Lab 6: Memory Leak - Review

Mark Gebbet — Mon, 21 Jul 2008 15:28:09 GMT

We have a similar problem to this demo. The modules have metadata as shown below. It looks like some sort of XSL transform generated assembly?

Has anyone else had this problem?

....K........<Mo

dule>.JScript 0.

Script3.System.X

ml.Xsl.CompiledQ

uery.Microsoft.J

Script.mscorlib.

GlobalScope.Comp

ilerGlobalScopeA

ttribute.System.

Runtime.Compiler

Services.ScriptO

bject.VsaEngine.

Microsoft.JScrip

t.Vsa.Import.Pac

kage.INeedEngine

.Object.System.L

ateBinding.Equal

ity.NumericBinar

y.Convert.Int32.

GlobalObject.Act

iveXObjectConstr

uctor.Boolean.Ru

ntimeTypeHandle.

SecurityTranspar

entAttribute.Sys

tem.Security.Ref

erenceAttribute.

.ctor.Global Cod

e..cctor..init.s

afeUri.base.uri.

GetEngine.SetEng

ine.vsa Engine.e

ngine.JScriptImp

ort.JScriptPacka

ge.ToObject.obj.

Call.EvaluateEqu

ality.GetNonMiss

ingValue.Evaluat

eNumericBinary.g

et_ActiveXObject

.CreateInstance.

SetValue.CreateE

ngineWithType.iw

a17tsd.JScript M

odule.....S.y.s.

t.e.m..%S.y.s.t.

e.m...C.o.l.l.e.

c.t.i.o.n.s...S.

y.s.t.e.m...T.e.

x.t..=S.y.s.t.e.

m...T.e.x.t...R.

e.g.u.l.a.r.E.x.

p.r.e.s.s.i.o.n.

s...S.y.s.t.e.m.

..X.m.l...S.y.s.

t.e.m...X.m.l...

X.s.l..!S.y.s.t.

e.m...X.m.l...X.

P.a.t.h...s.u.b.

s.t.r...i.n.d.e.

x.O.f...c.h.a.r.

A.t...l.e.n.g.t.

h...c.o.n.c.a.t.

..a.s.y.n.c...l.

o.a.d...p.a.r.s.

e.E.r.r.o.r...e.

r.r.o.r.C.o.d.e.

.././...:.../..-

M.s.x.m.l.2...D.

O.M.D.o.c.u.m.e.

n.t...4...0.....

.).....E...|...D

...?_....:..z\V.

4... ..... .....

.. ... ..... ...

. ......... ....

.......... ....

.............. .

........ .......

.=. ..... ......

...E...'......%.

).%.).%.).%.%.-.

).%.%.%.%.%.%.).

....R..MSystem.X

ml, Version=2.0.

0.0, Culture=neu

tral, PublicKeyT

oken=b77a5c56193

4e089..N..ISyste

m, Version=2.0.0

.0, Culture=neut

ral, PublicKeyTo

ken=b77a5c561934

e089..P..Kmscorl

ib, Version=2.0.

0.0, Culture=neu

tral, PublicKeyT

oken=b77a5c56193

4e089....-..

re: .NET Debugging Demos Lab 6: Memory Leak - Review

Tess — Mon, 04 Aug 2008 22:49:51 GMT

Actually this is a pretty common issue. It occurrs if you continously use the same XSLT transforms and the transforms use script blocks. To avoid it you should cache the transform or use precompiled code snippets

http://support.microsoft.com/?id=316775

re: .NET Debugging Demos Lab 6: Memory Leak - Review

Mark Gebbet — Thu, 21 Aug 2008 10:17:38 GMT

Thanks for the help. After your tip-off I tracked the problem to our content management system.