Why does out of memory exception arise on processing large size documents in Essential DocIO in Windows Phone ?
Essential DocIO keeps the entire document contents (paragraphs, images, tables and all other supported items along with the formatting) in main memory. Some documents may seem to have very less contents, but Essential DocIO uses more memory due to rich set of formatting applied to the contents. In case of opening a Docx file, you may think the file size is small but Essential DocIO utilizes very large memory. Whereas it is a zip archive file with extension “docx”, Essential DocIO internally decompress it and populate the content in the document object model utilizing remarkable main memory. The main memory utilized by an instance will not be released until the instance is removed from the document.
Hence there is a chance for “Out of memory exception” when the memory utilization exceeds the maximum level as the content of the document increases. Kindly split the contents to several documents or use high configuration machines with extended RAM such as to create or open large size documents comfortably.
I hope you enjoyed learning about why does out of memory exception arise on processing large size documents in Essential DocIO in Windows Phone.
You can refer to our Windows Phone feature tour page to know about its other groundbreaking feature representations and documentation, and how to quickly get started for configuration specifications. You can also explore our WindowsPhone Document libraries example to understand how to create and manipulate data.
If you have any queries or require clarifications, please let us know in the comments section below. You can also contact us through our support forums, Direct-Trac, or feedback portal. We are always happy to assist you!