Accessibility/Crash
From MozillaWiki
Contents
We have crashers
We can fix crashers
The crashing thread's frame stack is of course useful. Looking at this and the "Crash Reason" can sometimes be enough to know what's going on, and sometimes not.
STR (Steps to reproduce)
We don't often get useful comments in the crash reports so we must do some detective work.
Modules
On Windows DLL that match these patterns can indicate what screen reader might be useful in attempting to recreate the crash, since these can be injected into the gecko process.
- fsDOM* for JAWS
- GW* for GW Micro's Window-Eyes
- VBuf* for NVDA
Other patterns
- mzvkbd.dll is the Kaspersky Anti Virus virtual keyboard
- this seems to instantiate gecko accessibility
