Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Safari iOS memory error #10

Closed
dolbex opened this issue Feb 25, 2022 · 5 comments
Closed

Safari iOS memory error #10

dolbex opened this issue Feb 25, 2022 · 5 comments

Comments

@dolbex
Copy link

dolbex commented Feb 25, 2022

Running into an error when displaying multiple pages on a 4MB PDF.

Total canvas memory use exceeds the maximum limit (256 MB)" error in safari 12 and above

I've seen errors like this elsewhere that seem to be addressed: mozilla/pdf.js#11297

I forked this repo and updated the pdf-dist package and that didn't seem to help. Maybe my implementation is incorrect? Anybody run into this?

@hrynko
Copy link
Owner

hrynko commented Feb 25, 2022

At first glance, this looks like a Safari limitation. However, I'll try to find out if it is possible to resolve this within the library later.

@dolbex
Copy link
Author

dolbex commented Feb 25, 2022

That'd be awesome @hrynko - Yeah, we love the lib and have it so the user can switch between single and all pages and that's working great.... you know... except in Apple's darling.

@hrynko
Copy link
Owner

hrynko commented Jun 20, 2022

Hi @dolbex,

In version 1.1.3, a fix for canvas utilization was released. This can solve the single page view (when page prop is provided), but there may still be an issue with displaying the entire document. However, I will try to implement lazy loading (rendering) to solve this issue by the next minor version, as I see no other way so far.

@hoomb
Copy link

hoomb commented Aug 15, 2023

Hello @hrynko is there any workaround to fix this issue on multi page pdf documents?

@hrynko
Copy link
Owner

hrynko commented Sep 12, 2023

Hi @hoomb,

Please keep an eye on #161, I think this might be the solution

@hrynko hrynko mentioned this issue Sep 20, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants