FetchMessage System.OutOfMemoryException

Hi,
I'm using Aspose.Email.dll version 6.3.0.0 runtime version v2.0.50727
I'm getting a System.OutOfMemoryException similar to the one addressed in this ticket: NETWORKNET-34182
when I use MailMessage msg = client.FetchMessage(msgInfo.UniqueUri);

The error is: System.OutOfMemoryException: Exception of type 'System.OutOfMemoryException' was thrown.
at System.String.GetStringForStringBuilder(String value, Int32 startIndex, Int32 length, Int32 capacity)
at System.Text.StringBuilder.set_Capacity(Int32 value)
at System.Xml.BufferBuilder.ToString()
at System.Xml.XmlTextReaderImpl.ParseText()
at System.Xml.XmlTextReaderImpl.ParseElementContent()
at System.Xml.XmlTextReaderImpl.Read()
at System.Xml.XmlLoader.LoadNode(Boolean skipOverWhitespace)
at System.Xml.XmlLoader.LoadDocSequence(XmlDocument parentDoc)
at System.Xml.XmlLoader.Load(XmlDocument doc, XmlReader reader, Boolean preserveWhitespace)
at System.Xml.XmlDocument.Load(XmlReader reader)
at Aspose.Email.Exchange.Schema.Exchange_2013.ExchangeServiceBinding.GetReaderForMessage(SoapClientMessage message, Int32 bufferSize)
at System.Web.Services.Protocols.SoapHttpClientProtocol.ReadResponse(SoapClientMessage message, WebResponse response, Stream responseStream, Boolean asyncCall)
at System.Web.Services.Protocols.SoapHttpClientProtocol.Invoke(String methodName, Object[] parameters)
at Aspose.Email.Exchange.Schema.Exchange_2013.ExchangeServiceBinding.GetItem(GetItemType GetItem1)
at #=qSh7zwx61qSfx1O0$FuDdqGGM9b7m5mhULBcCneJwDsqD$Hwv8iJBiQcwFkvb92Lk.FetchMessage(String #=qScIXLkZy_qYklksG1dMCkg==)
It only happens with emails containing large attachments.
The OS I'm running is Windows 8.1 OS 64-bit, but the program I'm running is built on x86.
In one of your posts (https://forum.aspose.com/t/33943), you mentioned this was a .NET issue.
Is this still true, or have there been changes since this 2014 post.
I'm guessing my issue is with the x86 .net, but I'd like your confirmation.

Thank you,
Rick

Hi Rick,


Thank you for writing to Aspose Support team.

Since the issue was related to .NET framework and specific to 32-bit operating system, we haven’t tested it further as our API has nothing to do with it. We are not sure if Microsoft has solved anything similar in the latest .NET framework. If this issue hasn’t been addressed, this error will still arise while using the latest version of the API. Please feel free to write to us if you have any further query in this regard.