Chromium Code Reviews
chromiumcodereview-hr@appspot.gserviceaccount.com (chromiumcodereview-hr) | Please choose your nickname with Settings | Help | Chromium Project | Gerrit Changes | Sign out
(133)

Issue 1566693002: Moved parent_->SchedulePaint() to Views::SetFillsBoundsOpaquely() and Views::SchedulePaint(). (Closed)

Created:
4 years, 11 months ago by bruthig
Modified:
4 years, 11 months ago
Reviewers:
jonross, sadrul, sky
CC:
chromium-reviews, tfarina, tdanderson+views_chromium.org
Base URL:
https://chromium.googlesource.com/chromium/src.git@master
Target Ref:
refs/pending/heads/master
Project:
chromium
Visibility:
Public.

Description

Moved parent_->SchedulePaint() to Views::SetFillsBoundsOpaquely() and Views::SchedulePaint(). Reland of patchset #8 id:140001 of https://codereview.chromium.org/1461673002/ Original patchset was reverted here https://codereview.chromium.org/1560723002/ due to memory leaks in tests. TBR=sadrul@chromium.org,jonross@chromium.org,sky@chromium.org BUG=551492, 546683 Original issue's description: > This CL fixes a more general issue in Views that had a quick fix > that landed here: https://codereview.chromium.org/1460733002/ > > The general problem is that the layer owned by a parent View can > become dirty/stale when a child view is painting to it's own layer. > This CL fixes the problem by scheduling paints on the parent view > when it may be dirty. > > BUG=551492, 546683 > TEST=ViewLayerTest.NoCrashWhenParentlessViewSchedulesPaintOnParent > ViewLayerTest.ScheduledRectsInParentAfterSchedulingPaint > ViewLayerTest.ParentPaintWhenSwitchingPaintToLayerFromFalseToTrue > ViewLayerTest.NoParentPaintWhenSwitchingPaintToLayerFromTrueToTrue > > Committed: https://crrev.com/c8761106916aac604f30fb2223cdbfb2bd3ffda3 > Cr-Commit-Position: refs/heads/master@{#367536} Committed: https://crrev.com/5f90e3971ee381e0208ab3cb5dc6e9916f173487 Cr-Commit-Position: refs/heads/master@{#367831}

Patch Set 1 #

Unified diffs Side-by-side diffs Delta from patch set Stats (+66 lines, -4 lines) Patch
M chrome/browser/ui/views/toolbar/toolbar_button.cc View 1 chunk +0 lines, -4 lines 0 comments Download
M ui/views/view.h View 2 chunks +4 lines, -0 lines 0 comments Download
M ui/views/view.cc View 2 chunks +14 lines, -0 lines 0 comments Download
M ui/views/view_unittest.cc View 2 chunks +48 lines, -0 lines 0 comments Download

Messages

Total messages: 8 (2 generated)
commit-bot: I haz the power
CQ is trying da patch. Follow status at https://chromium-cq-status.appspot.com/patch-status/1566693002/1 View timeline at https://chromium-cq-status.appspot.com/patch-timeline/1566693002/1
4 years, 11 months ago (2016-01-06 15:10:55 UTC) #2
bruthig
jonross@, sadrul@, sky@, this is a re-land of a previous issue and I've marked you ...
4 years, 11 months ago (2016-01-06 15:11:33 UTC) #3
commit-bot: I haz the power
Committed patchset #1 (id:1)
4 years, 11 months ago (2016-01-06 16:03:57 UTC) #4
commit-bot: I haz the power
Patchset 1 (id:??) landed as https://crrev.com/5f90e3971ee381e0208ab3cb5dc6e9916f173487 Cr-Commit-Position: refs/heads/master@{#367831}
4 years, 11 months ago (2016-01-06 16:05:58 UTC) #6
sadrul
On 2016/01/06 15:11:33, bruthig wrote: > jonross@, sadrul@, sky@, this is a re-land of a ...
4 years, 11 months ago (2016-01-06 16:39:21 UTC) #7
bruthig
4 years, 11 months ago (2016-01-06 16:42:17 UTC) #8
Message was sent while issue was closed.
On 2016/01/06 16:39:21, sadrul wrote:
> On 2016/01/06 15:11:33, bruthig wrote:
> > jonross@, sadrul@, sky@, this is a re-land of a previous issue and I've
marked
> > you as TBR.  Review if you wish.
> 
> Did you need to update any code/tests to fix the leak?

I did, I guess I should have shown that delta between two patch sets in this
review.  Sorry.
Essentially I changed the parent_view to be allocated on the stack, as opposed
to the heap.

Powered by Google App Engine
This is Rietveld 408576698