<SDLErrorDetails time="16/01/2020 15:54:24">
<ErrorMessage>Exception of type 'System.OutOfMemoryException' was thrown.</ErrorMessage>
<Type>System.OutOfMemoryException, mscorlib, Version=126.96.36.199, Culture=neutral, PublicKeyToken=b77a5c561934e089</Type>
<StackTrace><![CDATA[ at System.String.ReplaceInternal(String oldValue, String newValue)
at System.String.Replace(String oldValue, String newValue)
at Sdl.FileTypeSupport.Bilingual.SdlXliff.XmlNodeBuilder.XmlBuilder.XmlEscape(String unescaped)
at Sdl.FileTypeSupport.Bilingual.SdlXliff.XmlNodeBuilder.XmlBuilder.AddText(String text)
at Sdl.FileTypeSupport.Bilingual.SdlXliff.FileManager.WriteZippedFile(XmlBuilder builder, String filePath)
at Sdl.FileTypeSupport.Bilingual.SdlXliff.XliffWriter.EmbedDependencyFile(XmlBuilder builder, IDependencyFileProperties file)
at Sdl.FileTypeSupport.Bilingual.SdlXliff.XliffWriter.AutoEmbedOrLinkDependencyFile(XmlBuilder builder, IDependencyFileProperties file)
at Sdl.FileTypeSupport.Bilingual.SdlXliff.XliffWriter.AddDependencyFile(XmlBuilder builder, IDependencyFileProperties file)
at Sdl.FileTypeSupport.Bilingual.SdlXliff.XliffWriter.SetDependencyFiles(FileSkeleton fileHeader, XmlBuilder builder)
at Sdl.FileTypeSupport.Bilingual.SdlXliff.XliffWriter.WriteFileComplete(FileSkeleton fileHeader, XliffFormattingXmlTextWriter writer)
at Sdl.FileTypeSupport.Bilingual.SdlXliff.XliffWriter.WriteSdlXliff(XliffFormattingXmlTextWriter writer)
at Sdl.TranslationStudio.Editor.TranslationEditor.TranslatableDocument.SaveBilingualImpl(String bilingualFilePaths, Boolean copy, IJobExecutionContext context, Boolean isAutoSaved)
at Sdl.TranslationStudio.Editor.TranslationEditor.TranslatableDocument.Save(IJobExecutionContext context)
at Sdl.TranslationStudio.Api.Editor.AbstractInternalDocument.SaveJobRequest.Execute(IJobExecutionContext context)
at Sdl.Desktop.Platform.Implementation.Services.Log.Resources(Object message, Action action)
at Sdl.Desktop.Platform.Implementation.Services.Job._worker_DoWork(Object sender, DoWorkEventArgs e)
at System.ComponentModel.BackgroundWorker.OnDoWork(DoWorkEventArgs e)
at System.ComponentModel.BackgroundWorker.WorkerThreadStart(Object argument)]]></StackTrace>
<ProductName>SDL Trados Studio</ProductName>
<OperatingSystem>Microsoft Windows 7 Professional </OperatingSystem>
<ServicePack>Service Pack 1</ServicePack>
I thought I was only having a problem saving multiple files (which may or may not be a result of the last studio update) but it appears the issue was (or has become) generic. I've tried a repair but no effect. I also restarted my PC. I can translate as usual but not save. The stacktrace appears to refer to a Microsoft issue. I haven't installed anything new recently. However I suppose it could be the result of a Windows update?
In the meantime I will try a Studio 2019 trial as a workaround in order to meet my deadlines.
Guidance gratefully accepted.
Perhaps try this article first to see if it helps with your problem:
If it doesn't help please log a case so a support engineer can help you. For licensing or installation issues that prevent you from working we have a route for all customers to get help. This can be achieved really quickly using this link:
You have two options:
1. Submit a case using a webform2. Use live chat to get a licence reset
You want to use the first option and make sure you give them a link to this thread so they have some history of what you have tried already.
Many thanks for the link to the article but it's no longer there - would you know where it's moved to?
Hello CATHERINE RUSHTON ,
Please try this link https://gateway.sdl.com/apex/communityknowledge?articleName=Out-of-memory-exception-error-happens-all-the-time-while-translating
If you are still having issues, please do log a free licensing and installation ticket via your SDL account-
Hi Steven, many thanks but I did try this to no avail. I was about to post an update to say that I'm having the same problem in the trial version of Studio 2019.
I'll log a support ticket now.
CATHERINE RUSHTON ,.
Thank you- could you report back and let us know what the problem solution was please.
The reply was:
Thank you for contacting SDL Support.
Please be aware that SDL Support will always help our customers who have an Installation or Licensing problem.
However, the described issue is not an Installation or Licensing request and I will archive this case.
I assume that Support thinks it's a RAM issue. That may be (although the problem was still occurring with Physical Memory at 50%) and I am waiting on delivery of a new PC this week so we'll see. Meanwhile I have split the file and I am now able to save the parts individually so I'll just have to hope it doesn't affect the final product.
Hi CATHERINE RUSHTON
Unless you have a really old PC, upgrading your RAM will probably not solve the issue (even with a brand new PC the same issue will happen). Studio cannot handle the file because it is too big, and as you found out the only way to work around the problem is to split up the file into smaller parts.
CATHERINE RUSHTON said:Meanwhile I have split the file and I am now able to save the parts individually so I'll just have to hope it doesn't affect the final product.
As Jesse mentioned, it does sound as though the file was simply too large for Studio to handle without splitting and as you have verified this already that seems to be the way to go. But also note that upgrading your PC probably won't fix this either if the problem really is the file size, so you may have to split it with the new PC too.
Many thanks for the replies. I've now confirmed with the customer that the Trados file is misbehaving at their end as well.
It's been a confusing few weeks with out of memory exceptions on smaller files and multiple file work as well, so I couldn't immediately put the problem down to file size.
To clarify, I'm overdue a new PC (it meets the minimum requirements for 2017 but is creaking with most CAT tools now, as well as browsing etc.) so this isn't what's prompting me to upgrade. However, as an experiment I'll try this file on the new setup when it's ready and report back just to close the loop.