Open
Bug 1187587
Opened 9 years ago
Updated 2 years ago
a11y causes 60s+ freezes
Categories
(Core :: Disability Access APIs, defect)
Tracking
()
UNCONFIRMED
People
(Reporter: bugzilla.mozilla.org, Unassigned)
References
Details
Attachments
(1 file)
|
294.63 KB,
image/png
|
Details |
a11y-lag.png
After long session uptimes I experience increasingly worse freezes.
Attempting to isolate the cause with the gecko profiler made a11y stick out in the results. See attached profiler screenshot.
I read somewhere that a11y is triggered by touch input and IMEs. Would force-disabling it have any impact on that functionality?
Running with accessibility.force_disabled = 1 seems to significantly improve performance without ill effect.
|
||
Comment 2•9 years ago
|
||
David, does this tie in with the other experimentation you were doing? Anything that sticks out in the profiler log (which I can't read due to it being a graphic)?
> (which I can't read due to it being a graphic)?
There seems to be no anonymize option for profiler outputs, so taking a screencap is the easiest way to minimize information leakage.
|
||
Updated•2 years ago
|
Severity: normal → S3
You need to log in
before you can comment on or make changes to this bug.
Description
•