Databases
StackOverflow2013
Postsdbo
POSystem.OutOfMemory exception when calling MemoryStream.ToArray() after serializing object with DataContractSerializer
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POSystem.OutOfMemory exception when calling MemoryStream.ToArray() after serializing object with DataContractSerializer
    primarykey
    data
    text
    <p>I am getting an intermittent "out of memory" exception at this statement:</p> <pre><code> return ms.ToArray(); </code></pre> <p>In this method:</p> <pre><code>public static byte[] Serialize(Object inst) { Type t = inst.GetType(); DataContractSerializer dcs = new DataContractSerializer(t); MemoryStream ms = new MemoryStream(); dcs.WriteObject(ms, inst); return ms.ToArray(); } </code></pre> <p>How can I prevent it? Is there a better way to do this?</p> <p>The length of ms is 182,870,206 bytes (174.4 MB)</p> <p>I am putting this into a byte array so that I can then run it through compression and store it to disk. The data is (obviously) a large list of a custom class that I am downloading from a WCF server when my silverlight application starts. I am serializing it and compressing it so it uses only about 6MB in isolated storage. The next time the user visits and runs the silverlight application from the web, I check the timestamp, and if good I just open the file from isolated, decompress it, deserialize it, and load my structure. I am keeping the entire structure in memory because the application is mostly geared around manipulating the contents of this structure.</p> <p>@configurator is correct. The size of the array was too big. I rolled by own serializer, by declaring a byte array of [list record count * byte count per record], then stuffed it directly myself using statements like this to stuff it:</p> <pre><code> Buffer.BlockCopy( BitConverter.GetBytes(node.myInt),0,destinationArray,offset,sizeof(int)); offset += sizeof(int); </code></pre> <p>and this to get it back:</p> <pre><code> newNode.myInt= BitConverter.ToInt32(sourceByteArray,offset); offset += sizeof(int); </code></pre> <p>Then I compressed it and stored it to isolated storage.</p> <p>My size went from 174MB with the DataContractSerializer to 14MB with mine. After compression it went from a 6MB to a 1MB file in isolated storage.</p> <p>Thanks to Configurator and Filip for their help.</p>
    singulars
    1. PO
      singulars
      1. PTAnswer
    1. This table or related slice is empty.
    1. PTQuestion
    1. This table or related slice is empty.
    1. USBrad Boyce
    plurals
    1. PL
      singulars
      1. LTLinked
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PO
      singulars
      1. PTAnswer
    2. PO
      singulars
      1. PTAnswer
    3. PO
      singulars
      1. PTAnswer
    1. This table or related slice is empty.
    1. COHow big is your object? This should only happen if your serialized data has a very large size. Or perhaps if you serialize many medium(100k or so) sized objects.
      singulars
      1. POSystem.OutOfMemory exception when calling MemoryStream.ToArray() after serializing object with DataContractSerializer
      1. USCodesInChaos
    2. COAre you expecting the serialized contract to be big? If so and you are going to do IO with the resulting bytes, you might try using a FileStream etc. directly--
      singulars
      1. POSystem.OutOfMemory exception when calling MemoryStream.ToArray() after serializing object with DataContractSerializer
      1. USantlersoft
    3. CO@code Edited post to show stream is 174.4 MB
      singulars
      1. POSystem.OutOfMemory exception when calling MemoryStream.ToArray() after serializing object with DataContractSerializer
      1. USBrad Boyce
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload