commit | b8e0ac731a4921f973bebe02ffac362974c86c34 | [log] [tgz] |
---|---|---|
author | Dan Clark <daniec@microsoft.com> | Tue Apr 23 03:28:58 2024 |
committer | Chromium LUCI CQ <chromium-scoped@luci-project-accounts.iam.gserviceaccount.com> | Tue Apr 23 03:28:58 2024 |
tree | db8fc95a7106a8c4b7abc9d4edd7aa058e11b1f0 | |
parent | 7abb5431e0b273e0409576a46893a2bd04589445 [diff] |
Pass visited set through in SlowGetValueForControlIncludingContentEditable The CL [1] attempted to fix a stack overflow issue from recursive accessible name references by ensuring that the visited set was passed all the way through from AXNodeObject::GetValueContributionToName to a possibly recursive operation in SlowGetValueForControlIncludingContentEditable. However, I failed to actually pass the visited set through all the way. This should have been caught by the test coverage I thought I added, but apparently I must have broken that trying to simplify it, and it no longer catches the stack overflow condition. So, here I'm ensuring that the visited set is actually passed through, modifying (and triple-checking) the original test so it actually catches the crash, and adding the alternative repro suggested in [2]. [1] https://chromium-review.googlesource.com/c/chromium/src/+/5388968 [2] https://issues.chromium.org/u/1/issues/335553723#comment3 Bug: 330720260, 335553723 Change-Id: I7c9bdc64653a45184a7a0aaa6fd8af90f347497f Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5468155 Reviewed-by: Benjamin Beaudry <benjamin.beaudry@microsoft.com> Commit-Queue: Dan Clark <daniec@microsoft.com> Cr-Commit-Position: refs/heads/main@{#1291056}
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.