Skip to content

Actually reset the PDFPageProxy._xfaPromise property as intended (PR 13069 follow-up) #13119

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

Merged
merged 1 commit into from
Mar 19, 2021

Conversation

Snuffleupagus
Copy link
Collaborator

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.)

…R 13069 follow-up)

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.)
Copy link
Contributor

@calixteman calixteman left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thank you for fixing this.

@calixteman calixteman merged commit 57e7557 into mozilla:master Mar 19, 2021
@Snuffleupagus Snuffleupagus deleted the _xfaPromise-reset branch March 19, 2021 10:55
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants