(In reply to James Teh [:Jamie] from comment #4)
I can't reproduce this freeze on any of the sites listed. :( Some questions:
Weird...We are able to reproduce the freeze on those listed websites. We are able to reproduce when both
accessibility.cache.enabled is set to
true and NVDA is running (version: 2022.3)
- Does the browser UI freeze or just the tab in question? For example, can you close the tab either with the mouse or control+w when this occurs?
The browser UI freezes. I'm unable to close the tab via mouse or control+w
- If the browser UI does freeze, do you eventually see the Windows "not responding" indicator?
- If the browser UI can still be used, are you able to take a profile using the Firefox Profiler? I may be able to use a profile to figure out what's going on.
Unfortunately, the browser UI freezes and Firefox is unusable.
- If the browser UI does freeze, we'll need to create a dump to figure out what's going wrong. Probably the simplest way to do this is to use crashfirefox64.exe. You'll need to get the process id of the main Firefox process and pass that to the command; e.g.
crashfirefox64.exe 12345, where 12345 is the process id of the main Firefox process. One way to get the process id of the main process is to use about:processes.
I was able to generate the crash report via the
crashfirefox64.exe tool: https://crash-stats.mozilla.org/report/index/4416b110-2c6e-4d14-bb3e-8f0fc0221005#tab-details
I've also generated a dump file via procdump ( I've sent it to you on slack)