AbortError: signal is aborted without reason #1772
Replies: 2 comments 3 replies
-
Well, for starters, setting workerSrc in useEffect looks shady. useEffect fires after render is committed, so technically, React-PDF might already be rendering, or at least trying to. |
Beta Was this translation helpful? Give feedback.
-
i'm also getting the same issue with react docs view import * as React from "react"; export default function DocsViewer(userdocs) { const docs = [ return ( View Docs {/* <Typography id="modal-modal-description" sx={{ mt: 2 }}> Duis mollis, est non commodo luctus, nisi erat porttitor ligula. */} ); } Uncaught runtime errors: |
Beta Was this translation helpful? Give feedback.
-
Firstly, I must say that react-pdf has been incredibly helpful and has greatly assisted me.
I'd like to express my gratitude for that. However, I've encountered an issue with an 'abort signal' error. Upon researching methods to resolve this error, I discovered that it may be occurring due to the large size of my PDF file. Additionally, I suspect that attempting to render a new PDF file while the previous one is still rendering could trigger this error, although I'm not entirely certain. Has anyone else experienced a similar issue, or does anyone have suggestions for resolving this error?
This is how I implement to my project:
I've actually decided to render each page of the PDF when scrolling, but I'm unsure of how to proceed and haven't been able to find a solution.
fyi: I use NextJS with Material UI
Beta Was this translation helpful? Give feedback.
All reactions