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

[mobiusy]

All PDF files have this issue.
PD216484A.pdf

Configuration:

• safari 12
• iPad (6th generation), system version: 12.1.4
• PDF.js version: 1.6.0

Steps to reproduce the problem:

1. Prepare one pdf file, more pages more better
2. Open safari and open pdf file via pdf.js
3. Do not close the tab, open an new tab and open the pdf file in same way
4. Repeat step 3 until the pdf file pages shows blank

What is the expected behavior?
Expected the pdf shows correctly event user do not close previous tab.

What went wrong?
Got errors in browser inspector:

More info:

1. I tried the latest version of pdf.js(2.3.200), this issue still exists.
2. IPAD OS 13 have the same issue.

Is this a safari bug or pdf.js has workaround to avoid blank pages?

[Snuffleupagus]

Duplicate of #11245.

PDF.js version: 1.6.0

Furthermore, that's not an official release and in any case that version is a few years old and consequently no longer supported.

[mobiusy]

Duplicate of #11245.

PDF.js version: 1.6.0

Furthermore, that's not an official release and in any case that version is a few years old and consequently no longer supported.

I replaced the old version with 2.3.200, and apply the fix of fix of 11245, the issue still exists.
I think it is not the same reason with #11245 , but it exceed the memory usage limit of safari browser on iPad OS.

[timvandermeij]

2.3.200 also doesn't contain the fix from that issue yet. I would suggest waiting for the next release or cherry-picking the fix if need be. Closing since this should be fixed then.

[mobiusy]

2.3.200 also doesn't contain the fix from that issue yet. I would suggest waiting for the next release or cherry-picking the fix if need be. Closing since this should be fixed then.

Thanks for your reply. I applied the fix of 11245 in 2.3.200, and my issue is not been fixed. On iPad OS 12.1.4, the isIOS() check works OK before the fix, userAgent match the /IPAD/ check. I appreciate if you can do more investigation.

[Stevebel]

I was having a similar issue when I embedded the viewer in my app. There is a known issue with Safari that prevents garbage collection of canvases.

There's already code in place that has a workaround to force memory to clear when scrolling through the PDF (PDFPageView.reset):

pdf.js/web/pdf_page_view.js

Lines 185 to 188 in 693240c

	// Zeroing the width and height causes Firefox to release graphics
	// resources immediately, which can greatly reduce memory consumption.
	this.canvas.width = 0;
	this.canvas.height = 0;

However, this code wasn't being run when I closed the viewer, so I added the following code before closing the viewer:

PDFViewerApplication.pdfViewer._pages.forEach(page => page.reset());

I don't have enough experience with this project to know if there are any edge cases where this causes issues, but in our testing nothing has come up and we no longer have a memory leak.

[Th3Fire]

pdf.js/web/base_viewer.js

Line 46 in 7b23476

const DEFAULT_CACHE_SIZE = 10;

I workaround by reduce DEFAULT_CACHE_SIZE which number less than 10.
Hope this will help whom facing this problem.

[seopei]

I am running into the same issue. Is there a fix available? I am using ng2-pdf-viewer (VadimDez/ng2-pdf-viewer#492)

[visuallization]

We run into the same issue on IOS Safari. @mobiusy did you find a way to solve it?

[mobiusy]

We run into the same issue on IOS Safari. @mobiusy did you find a way to solve it?
Not yet, hope safari can fix this issue

[kantsverma]

I am facing the same issues with IOS 15.1 in iPhone and Mac

Check detail over here

[jcsrb]

a related article https://pqina.nl/blog/total-canvas-memory-use-exceeds-the-maximum-limit/

[Snuffleupagus]

Given that we (obviously) cannot fix canvas-related memory handling problems in the Safari browser itself, and that Firefox is the primary development target for this library, let's close this old issue since it unfortunately doesn't really seem actionable here.