Issues Observed in GroupDocs.Total - Parser and Merger

We are currently performing a POC using GroupDocs.Total in our application (running on .NET 8, Windows Server 2019) and have encountered a couple of issues which we would like your assistance with.

1. Parser – Incorrect Encryption Detection

We observed that GroupDocs.Parser is returning IsEncrypted = true for certain sample files that are not password-protected or restricted.
These files can be opened and accessed normally without any credentials, so this behavior appears to be incorrect.

2. Merger – Hanging During PDF Merge

While using GroupDocs.Merger to merge non-protected PDF files, the process seems to hang indefinitely and does not complete.
This occurs even with sample PDFs and without any encryption applied.

Could you please:

  • Confirm if these are known issues or expected behaviours
  • Advise on possible fixes or workarounds
  • Suggest if any configuration changes or updates are required

We have attached the sample source code used for this POC for your reference.

Looking forward to your guidance.
TestGroupDocsTotal01.zip (425.1 KB)

@hindol.santra

Thank you for attaching the project with sample files. We’re analyzing the issue and update you as soon as we have any new information. The issue ID for reference is TOTALNET-365.

@hindol.santra

We have checked both issues and found a bug in Parser and as a result Parser returns incorrect value. This issue will be fixed in the next version of GroupDocs.Total for .NET 26.4, we planning to publish this version today but there can be some delays.

Furthermore we have discovered performance-related issue in Parser which requires more time to be fixed and can’t be delivered in this release therefore we do suggest using Viewer which is well optimized for this operation:

using (GroupDocs.Viewer.Viewer viewer = new GroupDocs.Viewer.Viewer(filePath)) 
{
    return viewer.GetFileInfo().Encrypted;
}

Unfortunately, we do not have any fix for the second issue with Merger except we discovered that the following line causes hang, so if you can work without this feature, comment it out till we could analyze it more deeply

pdfSaveOptions.AccesibilitySettings.EnableAutoTagging = true;