Use fuzzy-matching to improve cache hit rates with PostScriptEvaluator

src/core/function.js

@@ -447,16 +447,20 @@ class PDFFunction {
     // seen in our tests.
     const MAX_CACHE_SIZE = 2048 * 4;
     let cache_available = MAX_CACHE_SIZE;
-    const tmpBuf = new Float32Array(numInputs);
+    const input = new Float32Array(numInputs);
 
     return function constructPostScriptFn(src, srcOffset, dest, destOffset) {
       let i, value;
       let key = "";
-      const input = tmpBuf;
       for (i = 0; i < numInputs; i++) {
         value = src[srcOffset + i];
         input[i] = value;
-        key += value + "_";
+        // Fuzzy-match to increase the cache hit rate which helps improve
+        // performance, at the expense of absolute rendering quality.
+        // In practice this seems fine, and in the test-suite there are no
+        // perceivable differences, which is likely because the computed value
+        // will *eventually* be clamped to the [0, 255] range during rendering.
+        key += Math.round(value * 1e8) + "_";
       }
 
       const cachedValue = cache[key];

src/display/api.js

@@ -280,7 +280,7 @@ function getDocument(src) {
     Number.isInteger(src.maxImageSize) && src.maxImageSize > -1
       ? src.maxImageSize
       : -1;
-  const isEvalSupported = src.isEvalSupported !== false;
+  const isEvalSupported = false; // src.isEvalSupported !== false;
   const isOffscreenCanvasSupported =
     typeof src.isOffscreenCanvasSupported === "boolean"
       ? src.isOffscreenCanvasSupported

test/pdfs/pr5134.pdf.link

@@ -0,0 +1 @@
+https://web.archive.org/web/20140211020222/http://www.coachusa.com/CoachUsaAssets/files/97/route45.pdf

test/test_manifest.json

@@ -2230,6 +2230,15 @@
     "lastPage": 1,
     "type": "eq"
   },
+  {
+    "id": "pr5134",
+    "file": "pdfs/pr5134.pdf",
+    "md5": "6a701a163472e071a2519348b55cbac1",
+    "rounds": 1,
+    "link": true,
+    "firstPage": 2,
+    "type": "eq"
+  },
   {
     "id": "issue5599",
     "file": "pdfs/issue5599.pdf",