adobe / aem-core-wcm-components

Standardized components to build websites with AEM.
https://docs.adobe.com/content/help/en/experience-manager-core-components/using/introduction.html
Apache License 2.0
740 stars 747 forks source link

PDF Viewer Bookmarks Not Loading for large PDFs with lots of bookmarks #1569

Closed bowenaus closed 3 years ago

bowenaus commented 3 years ago

Bug Report

Current Behavior With the PDF Viewer core component, we are able to load small .pdfs with minimal amounts of bookmarks just fine. However, it is failing to load bookmarks with larger .pdfs containing a lot of bookmarks.

For example, when we use jmv16966.pdf.zip (attached), and click the bookmark icon to load the bookmarks, it momentarily shows a loading icon & then after a few seconds the bookmark icon disappears altogether. jmv16966.pdf (2).zip

This error also shows up in the browser console: AcrobatJS Version: 2.6.8 rendition.js:2 Error at self._cxa_throw (wasm_acrobat.js:1) at documentcloud.adobe.com/dc-rendition-provider/2.10.1_3.315.0/AJS/wasm_acrobat.wasm:wasm-function[1156]:0x23a9d at ZNK2t33pdf5store5ArrayINS1_14StoreObjTraitsINS_20TetraphiliaAppTraitsEEEE15GetRequiredNameEm (documentcloud.adobe.com/dc-rendition-provider/2.10.1_3.315.0/AJS/wasm_acrobat.wasm:wasm-function[1890]:0x37c91) at documentcloud.adobe.com/dc-rendition-provider/2.10.1_3.315.0/AJS/wasm_acrobat.wasm:wasm-function[11001]:0x159273 at documentcloud.adobe.com/dc-rendition-provider/2.10.1_3.315.0/AJS/wasm_acrobat.wasm:wasm-function[11009]:0x15a110 at documentcloud.adobe.com/dc-rendition-provider/2.10.1_3.315.0/AJS/wasm_acrobat.wasm:wasm-function[11008]:0x159fd8 at documentcloud.adobe.com/dc-rendition-provider/2.10.1_3.315.0/AJS/wasm_acrobat.wasm:wasm-function[11010]:0x15a24c at documentcloud.adobe.com/dc-rendition-provider/2.10.1_3.315.0/AJS/wasm_acrobat.wasm:wasm-function[11210]:0x164620 at dynCall_vii (documentcloud.adobe.com/dc-rendition-provider/2.10.1_3.315.0/AJS/wasm_acrobat.wasm:wasm-function[13127]:0x249f2d) at Object.Module.dynCall_vii (wasmacrobat.js:1) VM565:1 visitor.publishDestinations() result: The destination publishing iframe is already attached and loaded. rendition.js:2 AcrobatJS Version: 2.6.8 rendition.js:2 Error at self.cxa_throw (wasm_acrobat2.js:1) at documentcloud.adobe.com/dc-rendition-provider/2.10.1_3.315.0/AJS/wasm_acrobat2.wasm:wasm-function[1356]:0x31618 at dynCall_vii (documentcloud.adobe.com/dc-rendition-provider/2.10.1_3.315.0/AJS/wasm_acrobat2.wasm:wasm-function[15170]:0x2def82) at Object.Module.dynCall_vii (wasm_acrobat2.js:1) at invoke_vii (wasm_acrobat2.js:1) at ZNK2t33pdf5store5ArrayINS1_14StoreObjTraitsINS_20TetraphiliaAppTraitsEEEE15GetRequiredNameEm (documentcloud.adobe.com/dc-rendition-provider/2.10.1_3.315.0/AJS/wasm_acrobat2.wasm:wasm-function[2126]:0x4add5) at dynCall_viii (documentcloud.adobe.com/dc-rendition-provider/2.10.1_3.315.0/AJS/wasm_acrobat2.wasm:wasm-function[15173]:0x2defb4) at Object.Module.dynCall_viii (wasm_acrobat2.js:1) at invoke_viii (wasm_acrobat2.js:1) at documentcloud.adobe.com/dc-rendition-provider/2.10.1_3.315.0/AJS/wasm_acrobat2.wasm:wasm-function[12898]:0x1d3b1e VM565:1 visitor.publishDestinations() result: The destination publishing iframe is already attached and loaded.

Expected behavior/code The expected behavior would be that all of the bookmarks are loaded and accessible by the user inside of the embedded PDF.

Environment

)

Possible Solution

Additional context / Screenshots Add any other context about the problem here. If applicable, add screenshots to help explain.

Bookmarks begin loading. bookmarks-loading

Then, bookmark icon disappears altogether. User has no way of accessing any bookmarks. bookmarks-error-and-disappear

msagolj commented 3 years ago

Hi @bowenaus , the error is on the server side. The PDF Viewer is just a wrapper around the View SDK, so there is nothing we can do. I tested your file on the ViewSDK demo page:

https://documentcloud.adobe.com/view-sdk-demo/index.html#/customize/FULL_WINDOW

and got the same error. So i would suggest you contact adobe customer support and report the bug against the Document Services ViewSDK.