Open
Bug 1498743
Opened 6 years ago
Updated 2 years ago
Page freezes content process in mozilla::a11y::DocAccessible::ContentRemoved
Categories
(Core :: Disability Access APIs, defect, P2)
Core
Disability Access APIs
Tracking
()
NEW
People
(Reporter: jgilbert, Unassigned)
References
(Blocks 1 open bug, )
Details
It pretty much locks that content process until you say "kill the slow script please".
Comment 1•6 years ago
|
||
(In reply to Jeff Gilbert [:jgilbert] from comment #0)
> It pretty much locks that content process until you say "kill the slow
> script please".
Confirmed on OS X. I don't see aria-owns involved here [1], so it appears this is just a large page, where mutations kills down performance. Is there a chance to capture a perf profile?
https://www.khronos.org/registry/vulkan/specs/1.1-extensions/html/vkspec.html#devsandqueues-queues
Blocks: a11yperf
Priority: -- → P2
Comment 2•6 years ago
|
||
Just to clarify, does this page not hang content at all when a11y is disabled? I understand that a11y shows up as the culprit here, but I'm wondering whether that's indirect.
Comment 3•6 years ago
|
||
(In reply to James Teh [:Jamie] from comment #2)
> Just to clarify, does this page not hang content at all when a11y is
> disabled? I understand that a11y shows up as the culprit here, but I'm
> wondering whether that's indirect.
yes, this is a11y issue, it takes in secs when no a11y involved
Updated•2 years ago
|
Severity: normal → S3
You need to log in
before you can comment on or make changes to this bug.
Description
•