Skip to content
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

Jump to bottom

NVDA PDF Actual Text bug #7034

Closed
Wildted opened this issue Mar 30, 2017 · 1 comment
Closed

NVDA PDF Actual Text bug #7034

Wildted opened this issue Mar 30, 2017 · 1 comment
Assignees
@jcsteh
Labels
AdobeWork bug/app-crash p2 https://github.com/nvaccess/nvda/blob/master/projectDocs/issues/triage.md#priority
Milestone
2017.2

Comments

@Wildted
Copy link

Wildted commented Mar 30, 2017

There is currently a serious bug in NVDA as follows. If you add some Actual Text to a PDF tag and then delete the actual text again, an empty Actual Text attribute will be created in the PDF. This will cause NVDA to stop working completely (remain completely silent) on a Windows 7 machine. On a Windows 8 or Windows 10 machine, Acrobat or Adobe Reader will crash 100% of the time if you try to open such a file with NVDA running. This bug dos not affect JAWS, ZoomText, SuperNova, MAGic, Read&Write Gold or Claro Read.

The attached file that includes the word "Edit" is so affected (will crash). I also attach a version ("Original") which works fine.

For info I have experienced this bug in perhaps 50 different PDFs before I worked out what was going on (not just the attached files).

Thanks

Coram Life Education Bro 2015 - Edit.pdf
Coram Life Education Bro 2015 - Original.pdf
@jcsteh jcsteh added bug/app-crash p2 https://github.com/nvaccess/nvda/blob/master/projectDocs/issues/triage.md#priority AdobeWork labels Mar 30, 2017
@jcsteh
Copy link
Contributor

jcsteh commented Mar 31, 2017

The crash is the same as the first crash in #7021.

Technical: Getting the IPDDomNode for one of the nodes in this document
fails with E_FAIL for some reason and returns null. The crash is
because NVDA doesn't check for this and tries to dereference it. It
probably shouldn't be failing anyway, but that doesn't excuse the lack of a
check.

In this case, adding that check does fix the crash.

@jcsteh jcsteh self-assigned this Mar 31, 2017
This was referenced Mar 31, 2017
Merged
Closed
jcsteh added a commit that referenced this issue Apr 4, 2017
@jcsteh
Fix Acrobat Reader crash in PDF documents with empty ActualText attri…
2c9709e 
…butes. Incubates #7035 (issue #7034, #7021).
@nvaccessAuto nvaccessAuto added this to the 2017.2 milestone May 2, 2017
jcsteh added a commit that referenced this issue May 2, 2017
@jcsteh
Adobe Acrobat Reader no longer crashes in certain PDF documents (spec…
2e9e49f 
…ifically, those containing empty ActualText attributes). (PR #7035; issues #7021, #7034)

* Adobe Acrobat Reader no longer crashes in certain PDF documents (specifically, those containing empty ActualText attributes).

adobeAcrobat vbuf backend: get_PDDomNode can fail and return null, so check for a null pointer before trying to use it.

* Address review comments.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@jcsteh jcsteh

Labels
AdobeWork bug/app-crash p2 https://github.com/nvaccess/nvda/blob/master/projectDocs/issues/triage.md#priority
Projects
None yet
Milestone
2017.2
Development

No branches or pull requests
3 participants
@jcsteh @nvaccessAuto @Wildted