commit | 9d5c653161512b1fedd2be3e4784c6633e8f9388 | [log] [tgz] |
---|---|---|
author | Daniel Cheng <dcheng@chromium.org> | Fri Jun 28 20:02:36 2024 |
committer | Chromium LUCI CQ <chromium-scoped@luci-project-accounts.iam.gserviceaccount.com> | Fri Jun 28 20:02:36 2024 |
tree | e16a2e271e518f8d15c7ab169736e83211175cae | |
parent | c7f78a488ac419ea0966a356e178c9d7f10a7e99 [diff] |
Explicitly flush PhishyInteractionTracker logs before destruction Flushing at destruction time is too late since PhishyInteractionTracker is owned by a WebContentsUserData and calls WebContentsImpl virtual methods—specifically, WebContentsImpl::GetBrowserContext()—but WebContentsUserData destruction does not happen until WebContentsImpl's base classes are destroyed. Normally, the fix would be to explicitly clear the user data early in the destructor (e.g. see https://crrev.com/1313824); however, that turns out to be quite difficult here because: - WebContentsUserData cannot be destroyed before WebContentsDestroyed() is fired, and WebContentsDestroyed() is not fired until near the end of ~WebContentsImpl(). - WebContentsUserData cannot be destroyed before FrameTree, since there are DocumentUserData implementations that make the (reasonable) assumption that they will not outlive WebContentsUserData. This cannot be implemented without refactoring WebContents to use composition instead of inheritance for base::SupportsUserData. - Even with these adjustments, MSan *still* reports a use-after-dtor error, since WebContentsImpl::GetBrowserContext() delegates to the FrameTree's NavigationController to get the BrowserContext... but FrameTree (and NavigationController) are destroyed before WebContentsUserData. 💀 Instead, since ChromePasswordReuseDetectionManagerClient is already a WebContentsObserver and it also owns PhishyInteractiontracker, use WebContentsDestroyed() as a signal to flush the logs and add a DCHECK() to ~PhishyInteractionTracker() to ensure the logs were actually flushed. Bug: 40222690 Change-Id: I298df26d0bec7e1237d70f1568d3c7ed67f0929a Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5659460 Reviewed-by: Daniel Rubery <drubery@chromium.org> Commit-Queue: Daniel Cheng <dcheng@chromium.org> Cr-Commit-Position: refs/heads/main@{#1321152}
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.