Refresh cached attributes before name computation traversal.

It was possible to trigger a children clear operation while running
TextFromDescendants to compute a node name from its children. This
is the sequence:

* A node changes its aria-hidden value.
* We run TextFromDescendants on that node, it queries the hidden value
  for each child.
* To know the hidden value, it refreshes cached attributes in
  UpdateCachedAttributeValuesIfNeeded
* To refresh the cached aria-hidden value, it needs to check the
  parent's aria-hidden
* The parent also refreshes cached attributes in
  UpdateCachedAttributeValuesIfNeeded
* It detects aria-hidden value has changed, that triggers
  SetNeedsToUpdateChildren, which runs ClearChildren

To prevent children being cleared while we traverse them, which can
cause an invalid pointer being addressed, we run a refresh of cached
values before the traversal, knowing that operation may trigger a
children clear (and we will need to use those cached values anyway).

We also add a regression test, based on a clusterfuzz-generated one,
which is known to trigger this situation.

(cherry picked from commit 7880b4f179422725e67fef989a4f48bf5c0011c9)

Bug: 1315044
Change-Id: I0a7ca27cca5d93fbdbc07d31cab6a21b1401d8dc
AX-relnotes: prevent crash in name computation.
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/3633568
Commit-Queue: Jacobo Aragunde Pérez <jaragunde@igalia.com>
Reviewed-by: Aaron Leventhal <aleventhal@chromium.org>
Cr-Original-Commit-Position: refs/heads/main@{#1005708}
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/3655994
Bot-Commit: Rubber Stamper <rubber-stamper@appspot.gserviceaccount.com>
Cr-Commit-Position: refs/branch-heads/5060@{#175}
Cr-Branched-From: b83393d0f4038aeaf67f970a024d8101df7348d1-refs/heads/main@{#1002911}
4 files changed
tree: 91e7d14171cf3a22021872d8b05439efbd3e761b
  1. android_webview/
  2. apps/
  3. ash/
  4. base/
  5. build/
  6. build_overrides/
  7. buildtools/
  8. cc/
  9. chrome/
  10. chromecast/
  11. chromeos/
  12. codelabs/
  13. components/
  14. content/
  15. courgette/
  16. crypto/
  17. dbus/
  18. device/
  19. docs/
  20. extensions/
  21. fuchsia/
  22. fuchsia_webengine/
  23. gin/
  24. google_apis/
  25. google_update/
  26. gpu/
  27. headless/
  28. infra/
  29. ios/
  30. ipc/
  31. media/
  32. mojo/
  33. native_client_sdk/
  34. net/
  35. pdf/
  36. ppapi/
  37. printing/
  38. remoting/
  39. rlz/
  40. sandbox/
  41. services/
  42. skia/
  43. sql/
  44. storage/
  45. styleguide/
  46. testing/
  47. third_party/
  48. tools/
  49. ui/
  50. url/
  51. weblayer/
  52. .clang-format
  53. .clang-tidy
  54. .eslintrc.js
  55. .git-blame-ignore-revs
  56. .gitattributes
  57. .gitignore
  58. .gn
  59. .mailmap
  60. .rustfmt.toml
  61. .vpython
  62. .vpython3
  63. .yapfignore
  64. AUTHORS
  65. BUILD.gn
  66. CODE_OF_CONDUCT.md
  67. codereview.settings
  68. DEPS
  69. DIR_METADATA
  70. ENG_REVIEW_OWNERS
  71. LICENSE
  72. LICENSE.chromium_os
  73. OWNERS
  74. PRESUBMIT.py
  75. PRESUBMIT_test.py
  76. PRESUBMIT_test_mocks.py
  77. README.md
  78. WATCHLISTS
README.md

Logo Chromium

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.