Closed
Bug 395619
Opened 17 years ago
Closed 17 years ago
Unnacceptable find bar performance when a11y active
Categories
(Core :: Disability Access APIs, defect)
Core
Disability Access APIs
Tracking
()
RESOLVED
DUPLICATE
of bug 396005
People
(Reporter: aaronlev, Assigned: aaronlev)
References
Details
(Keywords: access, perf, regression)
With accessibility active, load
http://lxr.mozilla.org/seamonkey/source/accessible/src/base/nsRootAccessible.cpp
Try to search using Ctrl+F and typing a phrase.
It either is incredibly slow or locks up.
This does not happen when accessibility is not active.
Comment 1•17 years ago
|
||
Pretty sure you didn't mean to put this in Cmd-line Features :)
Assignee: nobody → aaronleventhal
Component: Cmd-line Features → Disability Access APIs
QA Contact: cmd-line → accessibility-apis
Comment 2•17 years ago
|
||
For what it's worth, even loading that page with accessibility enabled pretty much locks up for me. About 70% of the pageload time is spent under nsDocAccessible::FlushEventsCallback. Most of that is spent under nsDocAccessible::CreateTextChangeEventForNode. Lot of QI floating around, etc. Is there a separate bug on that stuff?
Back to this bug, I can't seem to reproduce it reliably. What phrase are you searching for?
Assignee | ||
Comment 3•17 years ago
|
||
Mozilla starts firing accessibility mutation and text change events once it 1) has a partial tree or 2) the page has fully loaded
#1 can happen early if there is any kind of focus, caret move or selection event in content
So, I think what's going on is that the new code to fire text change events is very expensive and if it starts happening before the page is fully loaded, it keeps calculating these events for every new bit of loaded content.
Comment 4•17 years ago
|
||
OK. Let's fix that, and see what happens here. I filed bug 396005.
Assignee | ||
Comment 5•17 years ago
|
||
In fact it's the same bug. Patch in bug 396005.
Status: NEW → RESOLVED
Closed: 17 years ago
Resolution: --- → DUPLICATE
You need to log in
before you can comment on or make changes to this bug.
Description
•