josephsl
commented
7 years ago Hi, which version of Windows is this, and did you try running NVDA without add-ons (if you have add-ons installed) to see if it improves things? Thanks.
From: abdullah5490 [mailto:notifications@github.com] Sent: Thursday, January 5, 2017 4:48 AM To: nvaccess/nvda nvda@noreply.github.com Cc: Subscribed subscribed@noreply.github.com Subject: [nvaccess/nvda] NVDA has an issue related to memory load in 2016.4 (#6701)
Hi the greatest team of nvAccess. Here is my another report about the most favourite screen reader for windows! In the latest release of NVDA, it has seam to be heavy footprint on the system memory/resources. The base of this report is the behaviour change of NVDA when system is doing some tasks in the background or forground, NVDA stop reading the focussed windows, stop reporting the opened windows while pressing alt+tab, and even not report the focus change to another windows. I have acer core i5 4th gen with 2.4GHZ along with turbo support, 6GB of RAM and $GB of NVIDIA as well as 3GB of intel HD graphic 4400. This type of specification is strong enough to handel every kind of software including screen reader. The regular performance of NVDA is good, but the problem began when there is some process going on! For example, If winRAR is extracting files from an archive at the time, and i want to use firefox to brows a web, NVDA does not told me to switch to the open windows, or navigate freely in the userinterface. Instead of this, it just announce the title of the windows with press of alt+tab, and does not allow to go inside that windows and use that software! Moreover, After this type of situation, NVDA stop reading the folder list in the "this PC" as well, even after completion of extraction. And it become neccessary to restart NVDA, or sometime need to restart the whole system to normalize its performance back to default state. This type of issue is not appears before this release. the 2016.3 sometime act in such way, but that was not obvious. BUt 2016.4 is becoming more problematic in such situations. The simple words to explain are, NVDA is not being able to handel the situation where system meory or processer is busy in doing some other tasks. I have varified this behaviour with different laptops, before reporting here. The case of winRAR extraction is just an example to explain my point, You can asume any type of task that may going on the system while initializing my report. Even most of the time, the simple process of copying files in my computer cause for this type of behaviour in the current release, while the previous releases are still working fine on the same machine.
— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub https://github.com/nvaccess/nvda/issues/6701 , or mute the thread https://github.com/notifications/unsubscribe-auth/AHgLkO_6llAm1L03iT_2pDJq3sHiQ8aKks5rPOZrgaJpZM4Lbp7j .
abdullah5490
feerrenrut
zahra21
LeonarddeR
Brian1Gaff
ehollig
Hi the greatest team of nvAccess. Here is my another report about the most favourite screen reader for windows! In the latest release of NVDA, it has seam to be heavy footprint on the system memory/resources. The base of this report is the behaviour change of NVDA when system is doing some tasks in the background or forground, NVDA stop reading the focussed windows, stop reporting the opened windows while pressing alt+tab, and even not report the focus change to another windows. I have acer core i5 4th gen with 2.4GHZ along with turbo support, 6GB of RAM and 4GB of NVIDIA as well as 3GB of intel HD graphic 4400. This type of specification is strong enough to handel every kind of software including screen reader. The regular performance of NVDA is good, but the problem began when there is some process going on! For example, If winRAR is extracting files from an archive at the time, and i want to use firefox to brows a web, NVDA does not told me to switch to the open windows, or navigate freely in the user interface. Instead of this, it just announce the title of the windows with press of alt+tab, and does not allow to go inside that windows and use that software! Moreover, After this type of situation, NVDA stop reading the folder list in the "this PC" as well, even after completion of extraction. And it become necessary to restart NVDA, or sometime need to restart the whole system to normalize its performance back to default state. This type of issue is not appears before this release. the 2016.3 sometime act in such way, but that was not obvious. But 2016.4 is becoming more problematic in such situations. The simple words to explain are, NVDA is not being able to handel the situation where system memory or processer is busy in doing some other tasks. I have varified this behaviour with different laptops, before reporting here. The case of winRAR extraction is just an example to explain my point, You can asume any type of task that may going on the system while initializing my report. Even most of the time, the simple process of copying files in my computer cause for this type of behaviour in the current release, while the previous releases are still working fine on the same machine.