Do you have an issue with a specific file(s)? Yes
Can you reproduce using one of our samples or online demos? Yes
Please give a brief summary of your issue:
(Think of this as an email subject)
PDF Compare is not loading due to calling DocumentViewer.startSemanticDiff
With specific pdf’s. The second pdf is larger (not sure if related)
Please describe your issue and provide steps to reproduce it:
(The more descriptive your answer, the faster we are able to help you)
Please provide a link to a minimal sample where the issue is reproducible:
Hello, I’m AiRon, an automated tech support bot While you wait for one of our customer support representatives, I can help you with your question.
It seems you’re encountering an issue with the DocumentViewer.startSemanticDiff method in WebViewer version 10.8.0, specifically when comparing two PDF files of different sizes. This can sometimes happen if the WebViewer struggles to process larger documents or if there is a mismatch in the document structure.
Some things you can try:
Ensure both PDF files are correctly formatted and not corrupted.
Check if the issue persists with smaller versions of the files or with other PDF files to isolate the problem to these specific documents.
Try increasing the memory allocation or performance settings in your environment to handle larger files.
Update to the latest version of WebViewer, as newer versions might have fixes for performance issues with document comparison.
Consider breaking down the larger document into smaller sections and compare them separately to identify any specific section causing the issue.
Here are some resources that might help you:
PDF Comparison Guide - Learn more about how PDF comparison works and common troubleshooting steps.
After investigating this issue it seems the issue is coming from your PDFs.
It seems the bounding boxes are corrupted, preventing WebViewer from detecting any text on the documents. That is why when opening the document on WebViewer, you are not able to select any text.
The feature you are trying to use is trying to compare the text between the two documents, by not finding any, the feature is sending an error.
Is there any way that webviewer can handle those hidden issues? Because acrobat viewer or other viewers and even the webviewer does not show errors or can handle the pdf to be shown. Only when comparing semantics is having issue that any client or us would not know because we already tried validating the pdf’s for issues but did not show any issues. Can we make the webviewer handle this internally if there are maybe incompatible elements?
Unfortunately, in this case, the PDF itself is the issue.
The issue is present on both WebViewer and Adobe, the bounding boxes are corrupted, which makes it tricky to detect the text for WebViewer. Adobe barely handles it.
Here is the difference when selecting text from our demo.pdf and yours:
Is it ok that that the compare in showcase would behave the same which is showing the loading indefinitely and no error prompt or other expected behavior?
