Repository navigation
Open
Labels
feature/magnifierp2https://github.com/nvaccess/nvda/blob/master/projectDocs/issues/triage.md#priorityhttps://github.com/nvaccess/nvda/blob/master/projectDocs/issues/triage.md#prioritytriagedHas been triaged, issue is waiting for implementation.Has been triaged, issue is waiting for implementation.
Milestone
Description
Sometimes, errors in virtual buffers cause Magnifier to flick and crash (deactivate itself):
- It sometimes happens when closing a Firefox tab (maybe 1/10 times)
- it happens with Character Information add-on when opening its report in a browseable message for some characters such as "𝔓".
- it also occurs in other situations.
Below is a 100% reproducible minimal test case constructed from the issue with Character Information add-on.
Steps to reproduce
- Enable Magnifier with inverted colors
- Open Python console
- enter the following and validate:
import ui;ui.browseableMessage("<p>𝔓 power set</p>", isHtml=True)
Actual behavior
- Magnifier crashes and reactivate 3 times, causing screen flicking.
- at the end, Magnifier remains disabled
- errors are logged
Expected behavior
- Magnifier should not crash. In case it cannot retrieve tracking information, it should filter the exception and log it. But the magnified view and color filters should remain active, even if tracking does not work for a time. If the duration where tracking does not work is expected to be long, e.g. more than 1 second or after focus / cursor have movee, it should be reported (e.g. with ui.message) that there is a tracking issue with the magnifier.
- If there is an issue making Magnifier crash, it should not attempt to relaunch itself. Indeed, this can cause flicking, with seizure risk as explained in Pause after changing magnifier colour filtering #20750. Moreover, I've never seen a situation where Magnifier crashes and reactivates successfully.
NVDA logs, crash dumps and other attachments
System configuration
NVDA installed/portable/running from source
Installed
NVDA version
2026.3beta2
Windows version
Windows 11 23H2 (AMD64) build 22631.7517
Name and version of other software in use when reproducing the issue
N/A
Other information about your system
N/A
Other questions
Does the issue still occur after restarting your computer?
- For this specific STR: not yet tested
- For crash/flicking issue in general (e.g. Firefox tab closing): yes
Have you tried any other versions of NVDA? If so, please report their behaviors
Yes. Same behaviour with 2026.2 (launcher).
If NVDA add-ons are disabled, is your problem still occurring?
Yes
Does the issue still occur after you run the System Accessibility Repair Tool in NVDA's tools menu?
Not tested
Metadata
Metadata
Assignees
Labels
feature/magnifierp2https://github.com/nvaccess/nvda/blob/master/projectDocs/issues/triage.md#priorityhttps://github.com/nvaccess/nvda/blob/master/projectDocs/issues/triage.md#prioritytriagedHas been triaged, issue is waiting for implementation.Has been triaged, issue is waiting for implementation.
Activity
CyrilleB79 commentedon Sep 17, 2026
@seanbudd given the work done in #20750, you may want to target this one for 2026.3, at least for the flicking part, i.e. to disable auto-relaunching of the magnifier.
The flicking risk in this issue is much more realistic than the one discussed in #20750.
seanbudd commentedon Sep 18, 2026
We will probably need to change the crash handling behaviour first to ensure the seizure risk is removed, and then look at addressing the crash possibly in a different release to 2026.3
CyrilleB79 commentedon Sep 22, 2026
Five days ago, I wrote in the initial description of this issue:
It's no longer true, even if probably not frequent. Here is the log:
Though, if it's low frequency, maybe we'd better investigate the root cause and fix it rather than triggering a magnifier reinitialization.
Limit magnifier max recovery attempts to 1 (#20897)