| commit | b5217aaf18adc12f972cfe5631c9a8fee43c306c | [log] [tgz] |
|---|---|---|
| author | Nick Birnie <birnie@google.com> | Wed Jul 23 19:31:36 2025 |
| committer | Chromium LUCI CQ <chromium-scoped@luci-project-accounts.iam.gserviceaccount.com> | Wed Jul 23 19:31:36 2025 |
| tree | c0294921ca3f28061601bce6a472bd3388f26b63 | |
| parent | e8384bc1a3d647ba41490eb06182e7b1aa0f5fc1 [diff] |
Revert "[ozone/wayland] Fix dangling pointer in `WaylandCursor`" This reverts commit 827a0cad64063079cf97d3aabfbdd9dbe620eeec. Reason for revert: Causing many Linux MSAN test failures: https://ci.chromium.org/ui/p/chromium/builders/ci/Linux%20MSan%20Tests/57522/overview Bug: 324294360 Original change's description: > [ozone/wayland] Fix dangling pointer in `WaylandCursor` > > Declare `seat_` before `cursor_` to prevent a dangling pointer issue. > This issue happens because the `cursor_` member holds a pointer to > `seat_->pointer_`, so `seat_` must be declared first to ensure it will > be destroyed last. > > Reset `cursor_` in WaylandPointer's destructor to prevent dangling > references. > > Bug: 324294360 > Change-Id: I0801545c62ad121349e05a4a39cbad0fc2105c20 > Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6757952 > Reviewed-by: Orko Garai <orko@igalia.com> > Reviewed-by: Max Ihlenfeldt <max@igalia.com> > Commit-Queue: AbdAlRahman Gad <agad@igalia.com> > Cr-Commit-Position: refs/heads/main@{#1490739} Bug: 324294360 Change-Id: I73993212ecd6eb699fd0aba32eb36b12cc94feb8 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6778487 Bot-Commit: Rubber Stamper <rubber-stamper@appspot.gserviceaccount.com> Reviewed-by: Nick Birnie <birnie@google.com> Owners-Override: Nick Birnie <birnie@google.com> Commit-Queue: Nick Birnie <birnie@google.com> Cr-Commit-Position: refs/heads/main@{#1491029}
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.