New issue
Advanced search Search tips
Note: Color blocks (like or ) mean that a user may not be available. Tooltip shows the reason.

Issue 612447 link

Starred by 1 user

Issue metadata

Status: WontFix
Owner:
Last visit > 30 days ago
Closed: May 2016
Cc:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 3
Type: Bug



Sign in to add a comment

WindowTreeClientImpl may observe windows after they have been freed

Project Member Reported by markdittmer@chromium.org, May 17 2016

Issue description

This was discovered while attempting to move tests from PlatformWindowMus to NativeWidgetMus (see build failure on https://codereview.chromium.org/1982663003/#ps1).

WindowTreeClientImpl::capture_window_ may be freed before WindowTreeClientImpl triggers observers on capture_window_. Naturally, triggering observers on the freed window can cause a crash.

This must be fixed by:

(1) Changing ownership model for windows that may become a WindowTreeClientImpl::capture_window_,
or
(2) Notifying WindowTreeClientImpl that its capture_window_ is being destroyed via an observer, callback, or similar.
 

Comment 1 by sadrul@chromium.org, May 17 2016

Cc: jamescook@chromium.org
Status: WontFix (was: Started)
This issue has either gone into hiding or resolved itself. The unittests that surfaced it are now passing.

Closing issue.

Sign in to add a comment