Get rid of raw pointer in WebContentsAccessibilityAndroid
This is a speculative fix. If WebContentsAccessibilityAndroid ever had a bad pointer to its root BrowserAccessibilityManager, that could definitely cause the sorts of crashes we've been seeing. Rather than keeping a copy of a raw pointer, just have WebContentsAccessibilityAndroid retrieve the root BrowserAccessibilityManager when needed. Also ensures that if GetRootBrowserAccessibilityManager is null, any function called from Java returns an error immediately, as that could also potentially be a source of bugs. Bug: 1126657 Change-Id: I52040a71c21ba4a8f5f30b316082c8b1e7efbb66 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2415928Reviewed-by:Mark Schillaci <mschillaci@google.com> Reviewed-by:
Bo <boliu@chromium.org> Commit-Queue: Dominic Mazzoni <dmazzoni@chromium.org> Cr-Commit-Position: refs/heads/master@{#808115}
Showing
This diff is collapsed.
Please register or sign in to comment