SingleProcessMash: Observed weird UI issue while scrolling webpage |
||||||||
Issue descriptionChromeOS 11587.0.0, 73.0.3669.0 dev-channel eve What steps will reproduce the problem? 1. Enable #single-process-mash flag from chrome://flags and click on the 'Restart No' button for the changes to take effect 2. Scroll through the chrome://flags page 3. Open a new browser tab and observe What happens ? Observed weird UI issues on scrolling and switching tabs. Observed this issue couple of times so far.
,
Jan 15
sky, it looks like only a single 256x256 or 512x512 graphics tile is updating during scrolling. Who is a good person for graphics issues?
,
Jan 15
Hopefully Sadrul or Mohsen could point us in the right direction.
,
Jan 15
,
Jan 16
Is it possible to see if there are any errors in the logs? Does chrome:gpu include any logs (look at the end of the page)?
,
Jan 16
(6 days ago)
Sadrul thinks this may be related to overlays. dcastagna@chromium.org, marcheu@chromium.org might either of you have any suggestions as to what might be going wrong, or what might not be configured correctly?
,
Jan 16
(6 days ago)
Sadrul thinks this may be related to overlays. dcastagna@chromium.org, marcheu@chromium.org might either of you have any suggestions as to what might be going wrong, or what might not be configured correctly?
,
Jan 16
(6 days ago)
,
Jan 16
(6 days ago)
I don't think this is related to HW overlays since I don't see any element in that page that would get promoted to one You can try to disable HW overlays in chrome://flags/#overlays-stratgies setting it to None and see if it still reproduces.
,
Jan 16
(6 days ago)
From a look at the video, this isn't overlay; this looks more likely to be a bug with > 1.0 scaling. Maybe scaling isn't handled properly with mash?
,
Jan 16
(6 days ago)
Looks like damage computation issue, although I couldn't repro on 73.0.3673.0 + nocturne (Slate) + SPM flag. Unfortunately, Chrome PFQ is broken and chrome haven't been uprev'ed yet. Gardener told me that it will be upreved either automatically or manually later today. sdantuluri@, could you please test again when new chrome hits canary?
,
Jan 16
(6 days ago)
sdantuluri, you'll need to explicitly turn on SingleProcessMash when new chrome hits canary.
,
Today
(9 hours ago)
I can't repro this. I tried SingleProcessMash with: * Official 73.0.3667 (11566) nocturne * ToT chrome r624798 (73.0.3681-ish, 11566) nocturne * ToT chrome r624160 (73.0.3677-ish, 11574) eve * ToT chrome r624798 (73.0.3681-ish, 11574) eve Perhaps this got fixed. Please reopen if you see it again. |
||||||||
►
Sign in to add a comment |
||||||||
Comment 1 by sdantul...@chromium.org
, Jan 15