XSL, Debugging and Memory Leak

While working on the Rainy Day Games site, we came across an unusual server behavior.  Memory allocated to the website pool kept growing and growing.  The site should be hanging around 65k was growing to over 1 Gig of memory!!!  So yeah, we had a classic leak.  Took a little bit of work but we traced it to the XSL object.  The parameter was set to true.  When it is true, it will create debugging information for the debugger to gather and report back to the developers.  As soon as we turned it off, the memory held.  Furthermore, once we cached the XSL object, we saw the average CPU utilization rate dropped by half.


Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s

%d bloggers like this: