CODEWITHSUNDEEP
c#jsonserializationjson.net
ashutosh raina
ashutosh raina

Reputation: 9314

Getting an OutOfMemoryException while serialising to JSON?

I am serializing , a MultiDictionary<String,Object>

http://powercollections.codeplex.com/ to json .

It has 618 elements with elements being deeply nested ,i.e. a single Object may have several dictionary like objects in it . I am using JSON.Net

String json = JsonConvert.SerializeObject(json, Newtonsoft.Json.Formatting.Indented);

what am i missing ?

MORE INFO: - This was working fine till i was using dynamic , i had to switch to MultiDictionary to allow multiple properties of the same name . It works for most cases , only when the number of items is large , it breaks .

UPDATE: -

I have been able to get a hold of the Memory consumption but cutting down on some elements that were getting added recursively to each element.

Upvotes: 14

Views: 36440

Answers (3)

Sam
Sam

Reputation: 1376

Assuming you don't have Circular References - if you can't store the whole thing in memory use a StreamWriter(JsonWriter or TextWriter) in Newtonsoft v4.0.30319

using (TextWriter writer = File.CreateText("LocalJSONFile.JSON"))
{
    var serializer = new JsonSerializer();
    serializer.Serialize(writer, myObject);
}

Use JsonWriter if you are trying to pass the string

StringBuilder sb = new StringBuilder();
StringWriter sw = new StringWriter(sb);

using(JsonWriter writer = new JsonTextWriter(sw))
{
  var serializer = new JsonSerializer();
  serializer.Serialize(writer, myObject);
}

Upvotes: 22

Tomislav Markovski
Tomislav Markovski

Reputation: 12346

It appears that you're running into Ciruclar Reference that is causing OutOfMemoryException or your objects are simply too large for your memory. Use NDepend to check this.

You might find useful getting the total size of your objects.

Upvotes: 13

&#211;scar L&#243;pez
&#211;scar L&#243;pez

Reputation: 235994

It's hard to tell without knowing the exact structure of the objects being serialized, but it's possible that, since the object graph is so big, there might be circular references somewhere (an object which points to an object which in turn points to the first object), creating an infinite loop of serialization.

EDIT :

You may use a tool, like NDepend, to find out where the circular references are. Give the trial version a try.

Upvotes: 2

Related Questions