Document comparison causes crash

GroupDocs.Comparison Product Family
,
1

Hello!

We have two Word documents that causes an exception when they are compared with GroupDocs.Comparison.

137.docx (35.0 KB)
237.docx (34.9 KB)

Comparing the documents produces the following exception:

Unhandled exception. GroupDocs.Comparison.Common.Exceptions.DocumentComparisonException: Error occurred in comparing Word documents
   at ☻▬§.☻(♣↑↨[] ☻, ♣↑↨[], CompareOptions ♣, ♥↨ ♠)
   at ↓.♥§♥▬☻(♥§ ☻, CompareOptions, SaveOptions ♣)
   at GroupDocs.Comparison.Comparer.☻(Stream ☻, Document, Document ♣, CompareOptions ♠, SaveOptions ♥, ♣§ )
   at GroupDocs.Comparison.Comparer.Compare(Stream document, SaveOptions saveOptions, CompareOptions compareOptions)

This code was run with GroupDocs.Comparison 24.4.0 in a .NET 6.0 console application on a Windows 11 machine:

using var comparer = new Comparer(loadPath1);
comparer.Add(loadPath2);
comparer.Compare(outputPath);

The exception is only thrown if document 137 is added first to the comparison. If document 237 is added first, the comparison produces an output document as expected.

When comparing the documents with the online tool we get the following error:

Error
Something went wrong
Server is not available

I suppose this is because of the same crash

1 Like
2

@lars.olsson
This issue is reproduced at our end. Therefore, 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-3990

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.

3

FYI @lars.olsson
The issue was fixed.
We’ll publish the fix within GroupDocs.Comparison for .NET 24.8 that will be published by the end of this month.

But to do not wait until official release here is a hotfix version that contains fix of this specific issue

1 Like
4

The issues you have found earlier (filed as COMPARISONNET-3990) have been fixed in this update. This message was posted using Bugs notification tool by anton.samarskyy