[ozone/wayland]Handle window destruction during surface configure ProcessPendingConfigureState() calls RequestStateFromServer(), which reaches the delegate's OnStateUpdate(). The views layer may synchronously close the widget and destroy the platform window inside that callout. The existing weak-ptr guard in MaybeApplyLatestStateRequest() returns early in that case, but ProcessPendingConfigureState() then continued to access members after the call returned. Add a weak-ptr liveness check around RequestStateFromServer(), mirroring the existing pattern used elsewhere in this file and in WaylandToplevelWindow::HandleToplevelConfigure(). Fixed: 518006275 Change-Id: I8812d780c4e46b42bc1a8302c69e4f2e8256b660 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/7981871 Commit-Queue: Kramer Ge <fangzhoug@chromium.org> Reviewed-by: Thomas Anderson <thomasanderson@chromium.org> Cr-Commit-Position: refs/heads/main@{#1651724}
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.