|
|
Descriptioncc : Fix effect tree index bug in cc::LayerImpl::Opacity
Since LayerImpl::Opacity of scrollbar layer can be called during layer's
PushPropertiesTo, we can't use the effect tree index in
LayerImpl::Opacity as its the new value but the new property trees
are pushed only after layer PushProperties.
BUG=616401
CQ_INCLUDE_TRYBOTS=tryserver.blink:linux_blink_rel
Committed: https://crrev.com/52c00185e5194c59dbbad339394eef256cd2b872
Cr-Commit-Position: refs/heads/master@{#397341}
Patch Set 1 #
Total comments: 5
Patch Set 2 : #
Messages
Total messages: 29 (13 generated)
Description was changed from ========== cc : Fix effect tree index bug in cc::LayerImpl::Opacity Since LayerImpl::Opacity of scrollbar layer can be called during layer's PushPropertiesTo, we can't use the effect tree index in LayerImpl::Opacity as its the new value but the new property trees are pushed only after layer PushProperties. BUG=616401 ========== to ========== cc : Fix effect tree index bug in cc::LayerImpl::Opacity Since LayerImpl::Opacity of scrollbar layer can be called during layer's PushPropertiesTo, we can't use the effect tree index in LayerImpl::Opacity as its the new value but the new property trees are pushed only after layer PushProperties. BUG=616401 CQ_INCLUDE_TRYBOTS=tryserver.blink:linux_blink_rel ==========
jaydasika@chromium.org changed reviewers: + ajuma@chromium.org, vollick@chromium.org
I couldn't exactly repro the bug (as there was no test case in the bug), but looking at the crash stack, I think this should fix the bug. https://codereview.chromium.org/2033453002/diff/1/cc/trees/layer_tree_host_im... File cc/trees/layer_tree_host_impl_unittest.cc (right): https://codereview.chromium.org/2033453002/diff/1/cc/trees/layer_tree_host_im... cc/trees/layer_tree_host_impl_unittest.cc:2900: EffectNode* pending_tree_node = This test will crash if we use effect_tree_index in LayerImpl::Opacity. The crash stack is the same as the one reported in the bug.
Just a question about the test. https://codereview.chromium.org/2033453002/diff/1/cc/trees/layer_tree_host_im... File cc/trees/layer_tree_host_impl_unittest.cc (right): https://codereview.chromium.org/2033453002/diff/1/cc/trees/layer_tree_host_im... cc/trees/layer_tree_host_impl_unittest.cc:2893: container->test_properties()->force_render_surface = true; Why do we need a surface here?
https://codereview.chromium.org/2033453002/diff/1/cc/trees/layer_tree_host_im... File cc/trees/layer_tree_host_impl_unittest.cc (right): https://codereview.chromium.org/2033453002/diff/1/cc/trees/layer_tree_host_im... cc/trees/layer_tree_host_impl_unittest.cc:2893: container->test_properties()->force_render_surface = true; On 2016/06/01 21:09:54, ajuma wrote: > Why do we need a surface here? Don't need a surface. I added this so that container gets an effect node and scrollbar layer's effect tree index changes.
Thanks, lgtm https://codereview.chromium.org/2033453002/diff/1/cc/trees/layer_tree_host_im... File cc/trees/layer_tree_host_impl_unittest.cc (right): https://codereview.chromium.org/2033453002/diff/1/cc/trees/layer_tree_host_im... cc/trees/layer_tree_host_impl_unittest.cc:2893: container->test_properties()->force_render_surface = true; On 2016/06/01 21:12:15, jaydasika wrote: > On 2016/06/01 21:09:54, ajuma wrote: > > Why do we need a surface here? > > Don't need a surface. I added this so that container gets an effect node and > scrollbar layer's effect tree index changes. Ah, makes sense. Please add a comment about that.
https://codereview.chromium.org/2033453002/diff/1/cc/trees/layer_tree_host_im... File cc/trees/layer_tree_host_impl_unittest.cc (right): https://codereview.chromium.org/2033453002/diff/1/cc/trees/layer_tree_host_im... cc/trees/layer_tree_host_impl_unittest.cc:2893: container->test_properties()->force_render_surface = true; On 2016/06/01 21:17:09, ajuma wrote: > On 2016/06/01 21:12:15, jaydasika wrote: > > On 2016/06/01 21:09:54, ajuma wrote: > > > Why do we need a surface here? > > > > Don't need a surface. I added this so that container gets an effect node and > > scrollbar layer's effect tree index changes. > > Ah, makes sense. Please add a comment about that. Done.
The CQ bit was checked by jaydasika@chromium.org
The patchset sent to the CQ was uploaded after l-g-t-m from ajuma@chromium.org Link to the patchset: https://codereview.chromium.org/2033453002/#ps20001 (title: " ")
CQ is trying da patch. Follow status at https://chromium-cq-status.appspot.com/patch-status/2033453002/20001 View timeline at https://chromium-cq-status.appspot.com/patch-timeline/2033453002/20001
The CQ bit was unchecked by commit-bot@chromium.org
Try jobs failed on following builders: linux_chromium_rel_ng on tryserver.chromium.linux (JOB_FAILED, http://build.chromium.org/p/tryserver.chromium.linux/builders/linux_chromium_...)
The CQ bit was checked by jaydasika@chromium.org
CQ is trying da patch. Follow status at https://chromium-cq-status.appspot.com/patch-status/2033453002/20001 View timeline at https://chromium-cq-status.appspot.com/patch-timeline/2033453002/20001
The CQ bit was unchecked by commit-bot@chromium.org
Try jobs failed on following builders: linux_chromium_rel_ng on tryserver.chromium.linux (JOB_FAILED, http://build.chromium.org/p/tryserver.chromium.linux/builders/linux_chromium_...)
The CQ bit was checked by jaydasika@chromium.org
CQ is trying da patch. Follow status at https://chromium-cq-status.appspot.com/patch-status/2033453002/20001 View timeline at https://chromium-cq-status.appspot.com/patch-timeline/2033453002/20001
The CQ bit was unchecked by commit-bot@chromium.org
Try jobs failed on following builders: linux_chromium_rel_ng on tryserver.chromium.linux (JOB_FAILED, http://build.chromium.org/p/tryserver.chromium.linux/builders/linux_chromium_...)
The CQ bit was checked by jaydasika@chromium.org
CQ is trying da patch. Follow status at https://chromium-cq-status.appspot.com/patch-status/2033453002/20001 View timeline at https://chromium-cq-status.appspot.com/patch-timeline/2033453002/20001
The CQ bit was unchecked by commit-bot@chromium.org
Try jobs failed on following builders: linux_chromium_rel_ng on tryserver.chromium.linux (JOB_FAILED, http://build.chromium.org/p/tryserver.chromium.linux/builders/linux_chromium_...)
The CQ bit was checked by jaydasika@chromium.org
CQ is trying da patch. Follow status at https://chromium-cq-status.appspot.com/patch-status/2033453002/20001 View timeline at https://chromium-cq-status.appspot.com/patch-timeline/2033453002/20001
Message was sent while issue was closed.
Committed patchset #2 (id:20001)
Message was sent while issue was closed.
Description was changed from ========== cc : Fix effect tree index bug in cc::LayerImpl::Opacity Since LayerImpl::Opacity of scrollbar layer can be called during layer's PushPropertiesTo, we can't use the effect tree index in LayerImpl::Opacity as its the new value but the new property trees are pushed only after layer PushProperties. BUG=616401 CQ_INCLUDE_TRYBOTS=tryserver.blink:linux_blink_rel ========== to ========== cc : Fix effect tree index bug in cc::LayerImpl::Opacity Since LayerImpl::Opacity of scrollbar layer can be called during layer's PushPropertiesTo, we can't use the effect tree index in LayerImpl::Opacity as its the new value but the new property trees are pushed only after layer PushProperties. BUG=616401 CQ_INCLUDE_TRYBOTS=tryserver.blink:linux_blink_rel Committed: https://crrev.com/52c00185e5194c59dbbad339394eef256cd2b872 Cr-Commit-Position: refs/heads/master@{#397341} ==========
Message was sent while issue was closed.
Patchset 2 (id:??) landed as https://crrev.com/52c00185e5194c59dbbad339394eef256cd2b872 Cr-Commit-Position: refs/heads/master@{#397341} |