Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Sync changes from mozilla-central gfx/wr #3907

Merged
merged 4 commits into from Apr 7, 2020
Merged

Conversation

@moz-gfx
Copy link

moz-gfx commented Apr 7, 2020

No description provided.

dblohm7 and others added 4 commits Apr 7, 2020
this is an attempt to handle tasks outside of the device bounds,
that belong to surfaces not establishing raster roots.

I suspect that the scaling we are now setting up in adjust_scale_for_max_surface_size
doesn't work properly, since the function was assumed to only affect the raster-rooted
surfaces. But it does fix the crash we have.

Differential Revision: https://phabricator.services.mozilla.com/D69654

[ghsync] From https://hg.mozilla.org/mozilla-central/rev/745c38db6468c26d2ee4c0cdfc5f9ec0b6733db9
The picture cache code retains a set of tiles that are currently
off-screen but might be needed again soon, depending on how the
page is scrolled.

However, off-screen tiles were being skipped during draw processing,
which meant that the texture cache request method was not being
called on these tiles. This would often result in the texture
cache eagerly evicting these seemingly unused surface tiles.

This patch re-arranges the occlusion and visibility processing
code for tiles, so that if a tile has been retained in the
picture cache grid, the texture surface is always requested,
even if that tile is currently off-screen. This prevents the
texture cache from evicting tiles that we want to retain for now.

Differential Revision: https://phabricator.services.mozilla.com/D69760

[ghsync] From https://hg.mozilla.org/mozilla-central/rev/c39512f89aedf7c0745137da9c8c09a54f9ab2e8
@moz-gfx
Copy link
Author

moz-gfx commented Apr 7, 2020

@bors-servo r=auto

@bors-servo
Copy link
Contributor

bors-servo commented Apr 7, 2020

📌 Commit 82bb470 has been approved by auto

@bors-servo
Copy link
Contributor

bors-servo commented Apr 7, 2020

Testing commit 82bb470 with merge 6878a88...

@bors-servo
Copy link
Contributor

bors-servo commented Apr 7, 2020

☀️ Test successful - status-appveyor, status-taskcluster
Approved by: auto
Pushing 6878a88 to master...

@bors-servo bors-servo merged commit 6878a88 into servo:master Apr 7, 2020
2 of 3 checks passed
2 of 3 checks passed
continuous-integration/appveyor/pr AppVeyor build failed
Details
Community-TC (pull_request) TaskGroup: success
Details
homu Test successful
Details
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Linked issues

Successfully merging this pull request may close these issues.

None yet

6 participants
You can’t perform that action at this time.