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 #3923

Merged
merged 2 commits into from Apr 18, 2020
Merged

Conversation

@moz-gfx
Copy link

moz-gfx commented Apr 17, 2020

No description provided.

aosmond and others added 2 commits Apr 17, 2020
…ty updates. r=kvark

The FrameTexturesUpdated event is intended to be issued when any
necessary texture cache updates have been completed for the current
frame. Originally we would simply check if the pending_texture_updates
vector in Renderer is empty. However the updates themselves could be
nops, and not trigger a timely frame render to occur, causing the
notifications to be delayed indefinitely. Now we track if there are
actually any pending specifically texture cache updates and only defer
the notification if true.

A consequence of deferring the notification indefinitely was revealed
when animating images just outside the current view. We would not
release the buffers for recycling even though we had no reason to hold
onto them. This could cause the image decoder to allocate new buffers
while the old buffers would not get released. It was not a true memory
leak because as soon as a frame is rendered, it would release all of the
old buffers, but it could easily cause a out of memory crash to occur if
the user was not interacting with the browser while in this state.

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

[ghsync] From https://hg.mozilla.org/mozilla-central/rev/3e0fdd643f2e134f6c278a2d3b17db172d2efa18
…r=jimb

This provides an implementation of linear filtering via the linear_blit
routine. That required factoring out textureLinear helper functions and
reusing them to do the actual filtering of the source texture.

Some collateral cleanups involved changing IntRect to use a start/end
format instead of origin/size, cleaner ways of getting offset texture
sampler pointers, and fixing clamping of linear filter coordinates.

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

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

moz-gfx commented Apr 17, 2020

@bors-servo r=auto

@bors-servo
Copy link
Contributor

bors-servo commented Apr 17, 2020

📌 Commit bdd8f68 has been approved by auto

@bors-servo
Copy link
Contributor

bors-servo commented Apr 17, 2020

Testing commit bdd8f68 with merge 84521c5...

@bors-servo
Copy link
Contributor

bors-servo commented Apr 18, 2020

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

@bors-servo bors-servo merged commit 84521c5 into servo:master Apr 18, 2020
3 checks passed
3 checks passed
Community-TC (pull_request) TaskGroup: success
Details
continuous-integration/appveyor/pr AppVeyor build succeeded
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

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