commit | 42d27da6f1a9d0035a6025755e7d7e2c0b1e19b7 | [log] [tgz] |
---|---|---|
author | kenoss <kenoss@chromium.org> | Tue Feb 25 10:52:44 2025 |
committer | Chromium LUCI CQ <chromium-scoped@luci-project-accounts.iam.gserviceaccount.com> | Tue Feb 25 10:52:44 2025 |
tree | 670e4c67f56c1b08a79d524800873410e0d939e1 | |
parent | 5333bc8f9293d4623ecedbfd8ed5c8b37dff1b65 [diff] |
[M134] Prerender2Fallback: Mitigate crash due to use-after-dtor of DocumentUserData We found that there is a case that uses `DevToolsPreloadStorage` after `DocumentAssociatedData::dtor()`, which is forbidden and cause a crash. To mitigate this, this CL calls `DevToolsPreloadStorage::GetOrCreateForCurrentDocument()` ahead and checks `DevToolsPreloadStorage::GetForCurrentDocument()` to get knowing `DocumentAssociatedData::dtor()` is already called or not. For more details, see https://docs.google.com/document/d/1ZP7lYrtqZL9jC2xXieNY_UBMJL1sCrfmzTB8K6v4sD4/edit?resourcekey=0-fkbeQhkT3PhBb9FnnPgnZA&tab=t.e4x3d1nxzmy3#heading=h.4lvl0yr9vmh7 (cherry picked from commit ec0728594435df87a6d68330661506577231aaba) Fixed: 394631076 Change-Id: I701ff6b0bb2bc50d4347d270dc4132490a437333 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6268901 Commit-Queue: Ken Okada <kenoss@chromium.org> Reviewed-by: Hiroki Nakagawa <nhiroki@chromium.org> Reviewed-by: Danil Somsikov <dsv@chromium.org> Cr-Original-Commit-Position: refs/heads/main@{#1421801} Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6285146 Auto-Submit: Ken Okada <kenoss@chromium.org> Commit-Queue: Hiroki Nakagawa <nhiroki@chromium.org> Cr-Commit-Position: refs/branch-heads/6998@{#1440} Cr-Branched-From: de9c6fafd8ae5c6ea0438764076ca7d04a0b165d-refs/heads/main@{#1415337}
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.