|
|
Chromium Code Reviews|
Created:
4 years, 7 months ago by Mark Dittmer Modified:
4 years, 7 months ago Reviewers:
sadrul CC:
chromium-reviews, rjkroege, Fady Samuel Base URL:
https://chromium.googlesource.com/chromium/src.git@master Target Ref:
refs/pending/heads/master Project:
chromium Visibility:
Public. |
DescriptionCandidate fix for observe-window-after-free error in WindowTreeClientImpl::LocalSetCapture
R=sadrul@chromium.org
BUG=612447
Patch Set 1 #Patch Set 2 : Call client->DestroyWindow from Window dtor rather than from window->Destroy #Patch Set 3 : Observer-based fix #Patch Set 4 : rebase #Patch Set 5 : Fix extra ref to capture_window_ #Patch Set 6 : Guard observer's AddObserver invocation #
Messages
Total messages: 31 (11 generated)
The CQ bit was checked by markdittmer@chromium.org to run a CQ dry run
Dry run: CQ is trying da patch. Follow status at https://chromium-cq-status.appspot.com/patch-status/1982333002/1 View timeline at https://chromium-cq-status.appspot.com/patch-timeline/1982333002/1
The CQ bit was unchecked by commit-bot@chromium.org
Dry run: Try jobs failed on following builders: chromeos_daisy_chromium_compile_only_ng on tryserver.chromium.linux (JOB_FAILED, http://build.chromium.org/p/tryserver.chromium.linux/builders/chromeos_daisy_...)
mus::Window::Destroy() calls WindowTreeClientImpl::DestroyWindow(). We should reset |capture_window_| in there. It looks like we do that correctly, but I think there are cases where we destroy a mus::Window (using mus::Window::LocalDestroy()) from some more places. One possibility is to call WindowTreeClientImpl::DestroyWindow() from ~Window(), instead of from Window::Destroy()
Call client->DestroyWindow from Window dtor rather than from window->Destroy
The CQ bit was checked by markdittmer@chromium.org to run a CQ dry run
Dry run: CQ is trying da patch. Follow status at https://chromium-cq-status.appspot.com/patch-status/1982333002/20001 View timeline at https://chromium-cq-status.appspot.com/patch-timeline/1982333002/20001
sadrul@chromium.org: New candidate fails some mash unit tests: https://build.chromium.org/p/tryserver.chromium.linux/builders/linux_chromium.... Investigating now.
The CQ bit was unchecked by commit-bot@chromium.org
Dry run: Try jobs failed on following builders: linux_chromium_gn_chromeos_rel on tryserver.chromium.linux (JOB_FAILED, http://build.chromium.org/p/tryserver.chromium.linux/builders/linux_chromium_...)
Observer-based fix
The CQ bit was checked by markdittmer@chromium.org to run a CQ dry run
Dry run: CQ is trying da patch. Follow status at https://chromium-cq-status.appspot.com/patch-status/1982333002/40001 View timeline at https://chromium-cq-status.appspot.com/patch-timeline/1982333002/40001
The CQ bit was unchecked by commit-bot@chromium.org
Dry run: Try jobs failed on following builders: chromeos_amd64-generic_chromium_compile_only_ng on tryserver.chromium.linux (JOB_FAILED, http://build.chromium.org/p/tryserver.chromium.linux/builders/chromeos_amd64-...) linux_chromium_gn_chromeos_rel on tryserver.chromium.linux (JOB_FAILED, http://build.chromium.org/p/tryserver.chromium.linux/builders/linux_chromium_...)
The CQ bit was checked by markdittmer@chromium.org to run a CQ dry run
rebase
Dry run: CQ is trying da patch. Follow status at https://chromium-cq-status.appspot.com/patch-status/1982333002/60001 View timeline at https://chromium-cq-status.appspot.com/patch-timeline/1982333002/60001
The CQ bit was unchecked by commit-bot@chromium.org
Dry run: Try jobs failed on following builders: cast_shell_linux on tryserver.chromium.linux (JOB_FAILED, http://build.chromium.org/p/tryserver.chromium.linux/builders/cast_shell_linu...) linux_chromium_gn_chromeos_rel on tryserver.chromium.linux (JOB_FAILED, http://build.chromium.org/p/tryserver.chromium.linux/builders/linux_chromium_...)
Fix extra ref to capture_window_
The CQ bit was checked by markdittmer@chromium.org to run a CQ dry run
Dry run: CQ is trying da patch. Follow status at https://chromium-cq-status.appspot.com/patch-status/1982333002/80001 View timeline at https://chromium-cq-status.appspot.com/patch-timeline/1982333002/80001
The CQ bit was checked by markdittmer@chromium.org to run a CQ dry run
Guard observer's AddObserver invocation
Dry run: CQ is trying da patch. Follow status at https://chromium-cq-status.appspot.com/patch-status/1982333002/100001 View timeline at https://chromium-cq-status.appspot.com/patch-timeline/1982333002/100001
sadrul@chromium.org: I'm advocating the current fix on the grounds that it works
The CQ bit was unchecked by commit-bot@chromium.org
Dry run: This issue passed the CQ dry run. |
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
