Assembly Caching and XmlSerializer

re: Assembly Caching and XmlSerializer

kaevans — Thu, 12 Feb 2004 01:17:00 GMT

I would still call this a bug personally. Several of the constructor overloads do reuse the dynamically created assembly, and there's no intrinsic reason the others could not do so as well. Maybe someone ran out of time, or patience, in creating the appropriate caching algorithms, and just decided these other cases weren't important enough. But anytime you run a loop over a few identical statements and "leak" more memory every time -- that's a bug! And yes, while the leak is actually a dynamically created assembly, the net result is that it still profoundly affects memory, so it is also a memory leak.

By the way, we had a rather interesting twist to this leak. We are using XmlSerialization to save user actions as reusable tasks. We also track their history to allow undos, and we save a portion of their history to allow them to get back to the same setup, kind of like a macro. OK, so lets say they performed a good number of tasks, each of which was serialized as part of their history. Each one of these tasks ends up being associated with a memory leak, but of course eventually they close the app and get the memory back. Oops! The gotcha for us was that the next time they can start from where they last left off, by having us reapply all of the tasks, which requires all the deserializations. The net result was that we instantly had a situation where we were actually recreating the very memory leaks from the last session!

re: Assembly Caching and XmlSerializer

kaevans — Thu, 12 Feb 2004 03:36:00 GMT

Paul,

Are you sure the memory really leaks, i.e. it's NEVER claimed by the garbage collection? Have you observed that the GC ran for all generations while you monitored memory usage? The fact that some assemblies are not cached doesn't mean they are leaked.

What exactly are you observing to determine that memory is leaking?

Also, the article Kirk quoted states that only some of more complex constructors of the XmlSerializer cause the XmlSerializer to not cache the temp assemblies. Is there a way to switch to simpler constructs?

Christoph

re: Assembly Caching and XmlSerializer

kaevans — Thu, 12 Feb 2004 13:53:00 GMT

Yes its a memory leak -- its NEVER reclaimed by the GC. Its the actual dynamic assembly that is "lost", which isn't managed memory. Some of the .net memory counters do increase a little, but its the private bytes of the process that go through the roof. Run this code snippet as the only file in a console app with performance monitor. With the leakMemory variable set to true, then run it again with leakMemory set to false. The only difference is whether or not the XmlSerializer is created each time, or only once. My last test had a fatal memory crash after leaking almost 500MB, which had long since pushed me far into the page file. All memory was reclaimed when the process was killed, or ended if you make it that far, but the GC never manages it or reclaims it. Can we switch to a simpler constructor? No. We could possibly use a different one with more work, but the other links I provided on my blog indicate that most of the constructors, except the very simplest, leak dynamic assemblies.

using System;
using System.IO;
using System.Text;
using System.Xml.Serialization;

namespace XmlLeak
{
class Global
{
private static bool leakMemory = true;
private static XmlSerializer serial = null;

[STAThread]
private static void Main(string[] args) {
for (int index = 0; index < 1000000; index++) {
Test test = new Test();
test.Id = index;
test.Time = DateTime.Now;
StringBuilder builder = new StringBuilder();
StringWriter writer = new StringWriter(builder);
if (leakMemory || serial == null) {
serial = new XmlSerializer(typeof(Base), new Type[] {typeof(Test)});
}
serial.Serialize(writer, test);
string xml = builder.ToString();
}
}
}

[Serializable()]
public class Test : Base
{
private DateTime time;
public DateTime Time {
get { return time; }
set { time = value; }
}
}

[Serializable()]
public class Base
{
private int id;
public int Id {
get { return id; }
set { id = value; }
}
}
}

re: Assembly Caching and XmlSerializer

kaevans — Sun, 12 Sep 2004 23:02:00 GMT

Any ways to get around the problem then?

re: Assembly Caching and XmlSerializer

kaevans — Fri, 22 Jul 2005 19:30:00 GMT

I share with you a workaround I found when serializing an ArrayList (when all the items are the same Type, that is "MyClass")

You'll see 3 examples:
1- Serializing the ArrayList "as is"
2- Caching the XmlSerlializer instance
3- Converting the ArrayList to a typed array

http://www.singletonsoftware.com.ar/XmlSerializer/SerTest.cs

Hope you find this useful.
Regards

Alejandro

Leaks with the XmlSerilizer?

TrackBack — Thu, 12 Feb 2004 03:39:00 GMT

Leaks with the XmlSerializer?

TrackBack — Thu, 12 Feb 2004 16:39:00 GMT

XML Bugs \ Inconsistencies in .NET 2.0: The MS Support Call Process : Migration Woes Part 2

Dan's Archive — Wed, 24 May 2006 15:56:57 GMT

XML Bugs \ Inconsistencies in .NET 2.0: The MS Support Call Process : Migration Woes Part 2

Dan's Archive — Fri, 04 Aug 2006 21:11:22 GMT

ANSWER: POP QUIZ: What to do next? - part 1

ASP.NET Debugging — Mon, 31 Mar 2008 17:56:26 GMT

So we didn't get much more on this one, so I'll go ahead and show how we find out what is going on here. 

Graco Nautilus 3 In 1 Car Seat

Graco Nautilus 3 In 1 Car Seat — Fri, 07 May 2010 11:12:23 GMT

I appreciated reading through your blog as well as I've recomeneded to my readers here's the hyperlink http://www.graconautilus3in1carseats.com/tag/graco-nautilus-3-in-1-car-seat/

free blogs for teachers

free blogs for teachers — Fri, 07 May 2010 19:08:05 GMT

We have been working on cranking out some new stuff for everyone. The latest is the Blogger Buddy gadget which allows you to quickly and easily view and post to your blogs on Blogger. com. It’ s still a little basic right now, but it gets the job done

working from home jobs

working from home jobs — Fri, 14 May 2010 11:23:20 GMT

Is credit card debt choking the life out of you? Using the credit card too often and incurring credit card debt seems to be today’ s disease. However, your predicament is partly the fault of credit card companies. They want to keep you in debt for as

free blog hosting service

free blog hosting service — Wed, 02 Jun 2010 07:04:59 GMT

Capture HD MP4 video and 5MP images and upload them directly to the Web1 with the Sony bloggie camera. The pocketable bloggie camera also features a unique swivel lens that rotates up to 270 degrees, making it easy to self- record a video clip. 1920 1080