-
Notifications
You must be signed in to change notification settings - Fork 6.6k
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Remove unnecessary function SerializerClearedNode()
The SerializerClearedNode() is part of some spidery code paths, where the AXObjectCache is called back by the serializer it owns. The extra complexity is not necessary, because: - The item that was being cleared, cached_bounding_boxes_, can be cleared in AXObjectCacheImpl when a node is removed, along other map entries for the node. This CL also updates RemoveAXID() to correctly clear other items as well. - The only reason to have this additional function is to avoid leaks when the serializer had to reset due to a failure. This almost never happens anymore, as we added DCHECKs for these failures and have cleaning up the majority of the causes. - Additional work in CL:4027071 will provide stable IDs for a11y objects that can have their own bounds, and therefore keeping the cached bounding box actually makes sense even in the rare case that the tree is reset. This alters now-invalid unit tests for the tree serializer that checked for leaks in situations that required tree resets. Bug: None Change-Id: I7300dceb1cc7e09adf38ff1620e8e64e9f262e10 Cq-Do-Not-Cancel-Tryjobs: true Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/3826007 Commit-Queue: Aaron Leventhal <aleventhal@chromium.org> Reviewed-by: David Tseng <dtseng@chromium.org> Cr-Commit-Position: refs/heads/main@{#1073689}
- Loading branch information
1 parent
5f332fe
commit 25ef2f6
Showing
8 changed files
with
13 additions
and
180 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters