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
fix: crash when saving edited PDF files #32512
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It looks like the patch needs an update to make sure fileName
is defined before its referenced.
4566ca3
to
558cb32
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Can you try upstreaming this? The chrome.fileSystem
API is apparently deprecated, so upstream might be interested in help moving off it :)
Release Notes Persisted
|
I have automatically backported this PR to "15-x-y", please check out #32537 |
I have automatically backported this PR to "16-x-y", please check out #32538 |
I have automatically backported this PR to "17-x-y", please check out #32539 |
Description of Change
Closes #32476.
This commit fixes a crash that persists any time a user attempts to download an edited PDF. This was happening because the logic flow for download of any edited PDF triggers a call to
chrome.fileSystem.chooseEntry
, which we do not support and which cause unmapped page access crashes.This patch can be removed should we choose to support
chrome.fileSystem
or support it enough to fix the crash.Checklist
npm test
passesRelease Notes
Notes: Fixed a crash that occurred when user attempted to download an edited PDF