Actually reset the PDFPageProxy._xfaPromise
property as intended (PR 13069 follow-up) (#13119)
Similar to the existing `annotationsPromise` and `_jsActionsPromise` properties, the new `_xfaPromise` should obviously also be reset, since otherwise you might end up holding onto a lot of data for pages that are no longer active. (That caching wasn't present in the original version of PR 13069, which is why I didn't spot it until now.)
This commit is contained in:
parent
24e598a895
commit
57e7557235
@ -1468,6 +1468,7 @@ class PDFPageProxy {
|
|||||||
this.objs.clear();
|
this.objs.clear();
|
||||||
this.annotationsPromise = null;
|
this.annotationsPromise = null;
|
||||||
this._jsActionsPromise = null;
|
this._jsActionsPromise = null;
|
||||||
|
this._xfaPromise = null;
|
||||||
this.pendingCleanup = false;
|
this.pendingCleanup = false;
|
||||||
return Promise.all(waitOn);
|
return Promise.all(waitOn);
|
||||||
}
|
}
|
||||||
@ -1502,6 +1503,7 @@ class PDFPageProxy {
|
|||||||
this.objs.clear();
|
this.objs.clear();
|
||||||
this.annotationsPromise = null;
|
this.annotationsPromise = null;
|
||||||
this._jsActionsPromise = null;
|
this._jsActionsPromise = null;
|
||||||
|
this._xfaPromise = null;
|
||||||
if (resetStats && this._stats) {
|
if (resetStats && this._stats) {
|
||||||
this._stats = new StatTimer();
|
this._stats = new StatTimer();
|
||||||
}
|
}
|
||||||
|
Loading…
Reference in New Issue
Block a user