commit | 2b67fc235eeb9cc40e88b5dbfc9af3c8366ff0f1 | [log] [tgz] |
---|---|---|
author | Chris Harrelson <chrishtr@chromium.org> | Fri Oct 27 01:52:47 2023 |
committer | Chromium LUCI CQ <chromium-scoped@luci-project-accounts.iam.gserviceaccount.com> | Fri Oct 27 01:52:47 2023 |
tree | 92379a1ca7b0a7a1183fd9161c7527a491a2f62d | |
parent | 1850fa325b0efbb6eb5fdac5946f804c4041b95e [diff] |
Avoid crashes when calling computedName or computedRole from DevTools The crash involves re-entrance to the rendering lifecycle. The lifecycle is supposed to be at pre-paint clean when these methods are called from devtools. However, the methods can also be called from the (not-shipped) AOM JS APIs. The code that checked for the lifecycle state in those methods was a hack to avoid re-entrant lifecycles. CL 4976744 revealed a situation when the lifecycle was not up-to-date (still don't know how); in those situations, return an empty string to avoid crashing. This CL also migrates DevTools to use a method that is guaranteed not to re-enter the lifecycle, which is a best practice for such situations. Fixed: 1496369 Change-Id: Ibeffd0169291897e208da6860320951078663153 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/4979375 Auto-Submit: Chris Harrelson <chrishtr@chromium.org> Reviewed-by: Mason Freed <masonf@chromium.org> Commit-Queue: Chris Harrelson <chrishtr@chromium.org> Cr-Commit-Position: refs/heads/main@{#1215890}
Chromium is an open-source browser project that aims to build a safer, faster, and more stable way for all users to experience the web.
The project's web site is https://www.chromium.org.
To check out the source code locally, don't use git clone
! Instead, follow the instructions on how to get the code.
Documentation in the source is rooted in docs/README.md.
Learn how to Get Around the Chromium Source Code Directory Structure .
For historical reasons, there are some small top level directories. Now the guidance is that new top level directories are for product (e.g. Chrome, Android WebView, Ash). Even if these products have multiple executables, the code should be in subdirectories of the product.
If you found a bug, please file it at https://crbug.com/new.