Dear SDL Devs and Community,

when processing huge projects through the Studio API with file based TMs exceeding 500mb and a big document e.g. a 27mb pdf file, we often see these kind of errors [1].

It is not possible to reproduce these errors reliably. Often our analysis step fails, sometimes also the pretranslate. We call the API as follows:

AutomaticTask analyzeTask = newProject.RunAutomaticTask(
files_to_analyse.GetIds(),
AutomaticTaskTemplateIds.AnalyzeFiles,
(sender, TaskStatus) => { taskStatusEventArgsList.Add(TaskStatus); },
(sender, AnalyzeMessage) => { messageEventArgsList.Add(AnalyzeMessage); }
);

We tried to include GC.Collect() on key steps (before doing the automatictasks, after saving the project in a previous step) as was suggested in this forum. But neither manual collection nor loading the FileBasedProject anew did help. When using the Visual Studio memory profiler, we observed a plateau at round 700 to 900mb during pretranslate or analysis.

Trados Studio itself seems to have a Thread- or memory-management based internal solution, which does not run out of memory with the same projects.

Is there some guidance what kind of code or calls we absolutely should avoid, to address this problem?

Best regards,

Hendrik @ Plunet

[1]

System.OutOfMemoryException: Eine Ausnahme vom Typ "System.OutOfMemoryException" wurde ausgelöst.
bei System.String.ReplaceInternal(String oldValue, String newValue)
bei System.String.Replace(String oldValue, String newValue)
bei Sdl.FileTypeSupport.Bilingual.SdlXliff.XmlNodeBuilder.XmlBuilder.XmlEscape(String unescaped)
bei Sdl.FileTypeSupport.Bilingual.SdlXliff.XmlNodeBuilder.XmlBuilder.AddText(String text)
bei Sdl.FileTypeSupport.Bilingual.SdlXliff.FileManager.WriteZippedFile(XmlBuilder builder, String filePath)
bei Sdl.FileTypeSupport.Bilingual.SdlXliff.XliffWriter.EmbedDependencyFile(XmlBuilder builder, IDependencyFileProperties file)
bei Sdl.FileTypeSupport.Bilingual.SdlXliff.XliffWriter.AutoEmbedOrLinkDependencyFile(XmlBuilder builder, IDependencyFileProperties file)
bei Sdl.FileTypeSupport.Bilingual.SdlXliff.XliffWriter.AddDependencyFile(XmlBuilder builder, IDependencyFileProperties file)
bei Sdl.FileTypeSupport.Bilingual.SdlXliff.XliffWriter.SetDependencyFiles(FileSkeleton fileHeader, XmlBuilder builder)
bei Sdl.FileTypeSupport.Bilingual.SdlXliff.XliffWriter.WriteFileComplete(FileSkeleton fileHeader, XliffFormattingXmlTextWriter writer)
bei Sdl.FileTypeSupport.Bilingual.SdlXliff.XliffWriter.WriteSdlXliff(XliffFormattingXmlTextWriter writer)
bei Sdl.FileTypeSupport.Bilingual.SdlXliff.XliffFileWriter.WriteSdlXliffToFile(String tempOutputFile)
bei Sdl.FileTypeSupport.Bilingual.SdlXliff.XliffFileWriter.Complete()
bei Sdl.FileTypeSupport.Framework.Integration.AbstractBilingualProcessorContainer.Complete()
bei Sdl.FileTypeSupport.Framework.Core.Utilities.BilingualApi.BilingualContentHandlerAdapter.Complete()
bei Sdl.FileTypeSupport.Framework.BilingualApi.AbstractBilingualContentProcessor.Complete()
bei Sdl.FileTypeSupport.Framework.BilingualApi.AbstractBilingualContentProcessor.Complete()
bei Sdl.FileTypeSupport.Framework.Core.Utilities.BilingualApi.BilingualContentHandlerAdapter.Complete()
bei Sdl.FileTypeSupport.Framework.Core.Utilities.BilingualApi.BilingualContentHandlerAdapter.Complete()
bei Sdl.FileTypeSupport.Framework.Integration.AbstractBilingualProcessorContainer.Complete()
bei Sdl.FileTypeSupport.Framework.Integration.MultiFileConverter.ParseNext()
bei Sdl.FileTypeSupport.Framework.Integration.MultiFileConverter.Parse()
bei Sdl.ProjectApi.Implementation.TaskExecution.ContentProcessingTaskImplementation.TaskFileExecuter.Parse(String targetFilePath)