Issue metadata
Sign in to add a comment
|
RenderAccessibilityImpl::SendPendingAccessibilityEvents can take a long time |
||||||||||||||||||||||||||
Issue descriptionLooking at Issue 777296 I noticed that RenderAccessibilityImpl::SendPendingAccessibilityEvents() can take 3 to 4ms on the Renderer Main Thread. It's longer than the Paint update. Steps from Issue 777296: Steps to reproduce the problem: 1. Open up Chrome 2. Go to http://m.shopping.daum.net/m/event/detail/3257 3. Scroll the page up & down Attached trace. Though this isn't a painting issue, adding Blink>Paint as this seems like something that could possibly be optimized by paint / rendering data structures.
,
Mar 6 2018
Hi gang. I believe that this issue is making input super laggy and Chrome overall feel extremely sluggish on my machine. I grabbed an ETW trace while typing some review comments into chromium-review.googlesource.com, and the renderer is using 100% of a core in this function. This doesn't seem right. I'm running 66.0.3358.0 (Official Build) canary (64-bit) (cohort: Clang-64), if it matters. Bumping to P1 and adding RBS since I don't think we should ship this. Assigning to dmazzoni@ for further triage. Thanks. Let me know if looking at the ETW trace I have would help.
,
Mar 19 2018
Friendly ping to get an update on this issue as it is marked as stable blocker. Thanks..!
,
Mar 26 2018
Gentle ping to get an update on this issue. Thanks..!
,
Apr 2 2018
Just a heads up, M66 Stable cut is on April 12th, 10 days away. This issue is marked as RB-Stable for 66. Please make sure to address this issue prior to stable cut. Thanks!
,
Apr 5 2018
ping @dmazzoni However, since Blink specific, marking with a11y-secondary label.
,
Apr 9 2018
This isn't a regression or anything new, and 99% of users don't have accessibility enabled. Merging with an existing bug that's similar. |
|||||||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||||||
Comment 1 by schenney@chromium.org
, Jan 2 2018Components: -Blink>Paint