From 2e6e2c3b41c19433f2c8a8b841375524fa1ae96a Mon Sep 17 00:00:00 2001
From: Jonas Jenwald <jonas.jenwald@gmail.com>
Date: Tue, 25 Aug 2020 11:25:08 +0200
Subject: [PATCH] Access the `XRef` data correctly in the "GetStats" handler in
 `src/core/worker.js`

Even though the code obviously works as-is, given that we have unit-tests for it, it still feels incorrect to just *assume* that the `XRef`-instance has all of its properties immediately available. Especially when (almost) all of the other handlers, in `src/core/worker.js`, protect their data accesses with appropriate `pdfManager.ensure` calls.
---
 src/core/worker.js | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/src/core/worker.js b/src/core/worker.js
index d2c680c53..5fe692bf5 100644
--- a/src/core/worker.js
+++ b/src/core/worker.js
@@ -507,7 +507,7 @@ class WorkerMessageHandler {
     });
 
     handler.on("GetStats", function wphSetupGetStats(data) {
-      return pdfManager.pdfDocument.xref.stats;
+      return pdfManager.ensureXRef("stats");
     });
 
     handler.on("GetAnnotations", function ({ pageIndex, intent }) {