[go: nahoru, domu]

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}
4 files changed
tree: e16a2e271e518f8d15c7ab169736e83211175cae
  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_web/
  22. gin/
  23. google_apis/
  24. google_update/
  25. gpu/
  26. headless/
  27. infra/
  28. ios/
  29. ipc/
  30. media/
  31. mojo/
  32. native_client_sdk/
  33. net/
  34. pdf/
  35. ppapi/
  36. printing/
  37. remoting/
  38. rlz/
  39. sandbox/
  40. services/
  41. skia/
  42. sql/
  43. storage/
  44. styleguide/
  45. testing/
  46. third_party/
  47. tools/
  48. ui/
  49. url/
  50. webkit/
  51. .clang-format
  52. .clang-tidy
  53. .clangd
  54. .eslintrc.js
  55. .git-blame-ignore-revs
  56. .gitallowed
  57. .gitattributes
  58. .gitignore
  59. .gitmodules
  60. .gn
  61. .mailmap
  62. .rustfmt.toml
  63. .vpython3
  64. .yapfignore
  65. ATL_OWNERS
  66. AUTHORS
  67. BUILD.gn
  68. CODE_OF_CONDUCT.md
  69. codereview.settings
  70. CPPLINT.cfg
  71. DEPS
  72. DIR_METADATA
  73. LICENSE
  74. LICENSE.chromium_os
  75. OWNERS
  76. PRESUBMIT.py
  77. PRESUBMIT_test.py
  78. PRESUBMIT_test_mocks.py
  79. README.md
  80. 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.