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

NVDA quits working with new tabs in IE and Firefox after reloading plugins #2892

Closed
nvaccessAuto opened this Issue Dec 23, 2012 · 2 comments

Comments

Projects
None yet
1 participant
@nvaccessAuto

nvaccessAuto commented Dec 23, 2012

Reported by katalina on 2012-12-23 00:00
After reloading plugins with CTRL+NVDA+F3, NVDA does not enter browse mode in new tabs or after clicking links from existing pages with IE and Firefox. Already opened tabs seem to be uneffected until a link is selected.
You can only navigate the page as if you are in focus mode, regardless of toggling the state with NVDA+Space.
restarting IE, Firefox, or NVDA fixes the issue.


Steps to reproduce:

Open IE or Firefox.
Go to some web page.
Reload plugins with CTRL+NVDA+F3
Open a new tab, and go to another webpage, or select a link from an open page.
Attempt to navigate.


Expected results:

Ability to navigate new page in browse mode.

Actual results:

Unable to enter browse mode.

Blocking #3646

@nvaccessAuto

This comment has been minimized.

Show comment
Hide comment
@nvaccessAuto

nvaccessAuto Dec 23, 2012

Attachment nvda.log added by katalina on 2012-12-23 00:01
Description:
NVDA Log file. Windows error is shown in log when a new tab is opened after reloading plugins.

nvaccessAuto commented Dec 23, 2012

Attachment nvda.log added by katalina on 2012-12-23 00:01
Description:
NVDA Log file. Windows error is shown in log when a new tab is opened after reloading plugins.

@nvaccessAuto

This comment has been minimized.

Show comment
Hide comment
@nvaccessAuto

nvaccessAuto Dec 26, 2012

Comment 1 by jteh on 2012-12-26 08:11
The reload plugins command has always had the potential to cause memory leaks and other breakage.

This particular issue occurs because destroying an app module causes NVDA to lose its connection to nvdaHelperRemote in the remote process. This connection is created by nvdaHelperRemote, not NVDA itself, so I don't think there's a way to re-establish this.

Mick, is there any easy way to work around this? Issues like this make me wonder whether we should drop the reload plugins command altogether.

nvaccessAuto commented Dec 26, 2012

Comment 1 by jteh on 2012-12-26 08:11
The reload plugins command has always had the potential to cause memory leaks and other breakage.

This particular issue occurs because destroying an app module causes NVDA to lose its connection to nvdaHelperRemote in the remote process. This connection is created by nvdaHelperRemote, not NVDA itself, so I don't think there's a way to re-establish this.

Mick, is there any easy way to work around this? Issues like this make me wonder whether we should drop the reload plugins command altogether.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment