Skip to main content
D
defaultbssold8ngxvl
Participating Frequently
January 6, 2022
Question

WASM error message

  • January 6, 2022
  • 1 reply
  • 1094 views

Hello,

I'm having an issue that is preventing our users from viewing documents. Everything on our backend and frontend are working properly, however I'm getting an error from the Adobe SDK WASM that doesn't provide any clues as to what's going on. Right now, the way our PDFs are loading are through a binary file stored in Redis in our backend, and then renders in React. Each step of the process successfully completes, so it looks like something entirely on Adobe's side. Here's the error message:

 

AcrobatJS Version: 2.6.68

rendition.js:2 Error

    at self.___cxa_throw (documentcloud.adobe.com/dc-rendition-provider/2.18.3_3.394.0/AJS/wasm_acrobat.js:1)

    at documentcloud.adobe.com/dc-rendition-provider/2.18.3_3.394.0/AJS/wasm_acrobat.wasm

    at documentcloud.adobe.com/dc-rendition-provider/2.18.3_3.394.0/AJS/wasm_acrobat.wasm

    at documentcloud.adobe.com/dc-rendition-provider/2.18.3_3.394.0/AJS/wasm_acrobat.wasm

    at documentcloud.adobe.com/dc-rendition-provider/2.18.3_3.394.0/AJS/wasm_acrobat.wasm

    at documentcloud.adobe.com/dc-rendition-provider/2.18.3_3.394.0/AJS/wasm_acrobat.wasm

    at documentcloud.adobe.com/dc-rendition-provider/2.18.3_3.394.0/AJS/wasm_acrobat.wasm

    at documentcloud.adobe.com/dc-rendition-provider/2.18.3_3.394.0/AJS/wasm_acrobat.wasm

    at Object.Module.dynCall_viii (documentcloud.adobe.com/dc-rendition-provider/2.18.3_3.394.0/AJS/wasm_acrobat.js:1)

    at invoke_viii (documentcloud.adobe.com/dc-rendition-provider/2.18.3_3.394.0/AJS/wasm_acrobat.js:1)

    This topic has been closed for replies.

    1 reply

    Raymond Camden
    Community Manager
    Raymond CamdenCommunity Manager
    Community Manager
    January 6, 2022

    Any chance this is online in a public place where I can take a look?

    D
    defaultbssold8ngxvlAuthor
    Participating Frequently
    January 7, 2022

    No, but we were able to get this resolved actually. This turns out to be an error when you try to render anything other than a PDF (we were not aware that we'd be getting any other file types than a PDF).

    Raymond Camden
    Community Manager
    Raymond CamdenCommunity Manager
    Community Manager
    January 7, 2022

    Oh wow, this is good to know actually. I can file a bug report to handle this nicer I think.

    Terms & ConditionsAccessibility statement
    Using the community Terms of use Privacy Cookie preferences Do not sell or share my personal information ad choicesAdChoices