Our product is using GroupDocs.Comparison to compare different versions of a document. One of our customers currently has problem with comparison of a few different documents. The comparison starts, but never terminates. The customer is also experiencing memory leakage related to this which eventually leads to the application crashing. I made a simple console app to isolate the problem, but the same error still occurs. I provide the code from my console app and three documents that cause the issue.
LicenseHandler.SetLicense();
const string loadPath1 = @"Documents\08456-1.docx";
const string loadPath2 = @"Documents\08456-2.docx";
const string outputPath = @"Output\08456-result.docx";
var compareOptions = new CompareOptions
{
DetectStyleChanges = false,
GenerateSummaryPage = false
};
using var doc1 = new FileStream(loadPath1, FileMode.Open);
using var doc2 = new FileStream(loadPath2, FileMode.Open);
using var comparer = new Comparer(doc1);
comparer.Add(doc2);
using var outputStream = File.Create(outputPath);
comparer.Compare(outputStream, compareOptions);
We would also like to know if there is anything within the documents that causes the problem so that we could let our customer know a potential temporary work around.
I added the project as a zip file in the shared folder that is linked above. It is a .NET 6 project and my own machine is runs Windows 11. We have reproduced the error in multiple Windows environments.
@lars.olsson
We have opened the following new ticket(s) in our internal issue tracking system and will deliver their fixes according to the terms mentioned in Free Support Policies.
Issue ID(s): COMPARISONNET-3379
You can obtain Paid Support services if you need support on a priority basis, along with the direct access to our Paid Support management team.
Thanks, since this is a major issue for several of our clients it would be mush appreciated if we could get more information regarding the issue. Can you please help us with that?
What causes the problem in the comparisons that fail?
In some cases we have seen that the issue causes a memory leakage that eventually will make the entire server crash. Have you seen this behaviors’? And what factors can cause this critical failure?
The issues you have found earlier (filed as COMPARISONNET-3379) have been fixed in this update. This message was posted using Bugs notification tool by anton.samarskyy
Is it possible for you to release a hotfix for this issue in a previous release. We have affected customers on the 22.6.0, 22.8.0 and the 22.11.0 release?