WebM rendered skewed on macOS
Categories
(Core :: Graphics: Layers, defect)
Tracking
()
| Tracking | Status | |
|---|---|---|
| firefox-esr60 | --- | unaffected |
| firefox66 | --- | unaffected |
| firefox67 | + | verified |
| firefox68 | + | verified |
People
(Reporter: denschub, Assigned: mstange)
References
(Blocks 1 open bug, Regression, )
Details
(Keywords: regression)
Attachments
(6 files)
|
2.60 KB,
text/html
|
Details | |
|
890 bytes,
text/html
|
Details | |
|
47 bytes,
text/x-phabricator-request
|
pascalc
:
approval-mozilla-beta+
|
Details | Review |
|
47 bytes,
text/x-phabricator-request
|
pascalc
:
approval-mozilla-beta+
|
Details | Review |
|
47 bytes,
text/x-phabricator-request
|
pascalc
:
approval-mozilla-beta+
|
Details | Review |
|
47 bytes,
text/x-phabricator-request
|
pascalc
:
approval-mozilla-beta+
|
Details | Review |
This WebM is rendered with a 45 degrees skew on macOS in Nightly, see the attached screenshot. This works fine in Release and on Windows in Nightly. Running mozregression returned this push, and bug 1479145 jumps out as something that could be related.
Requesting tracking for 67 and 68, because the issue is reproducible in 67, and the patch in question got uplifted.
| Reporter | ||
Comment 1•6 years ago
|
||
Markus, do you have an idea on what might cause this?
| Reporter | ||
Updated•6 years ago
|
Comment 2•6 years ago
|
||
This is very likely caused by bug 1479145.
Comment 3•6 years ago
|
||
Tracking for 67, if we can't get a fix before Beta 13 for this regression, we will back out bug 1479145 from beta.
| Assignee | ||
Comment 4•6 years ago
|
||
This is a WebM with alpha information, so YUV->RGBA conversion is done on the CPU. We're not respecting the correct stride in that code path.
| Assignee | ||
Comment 5•6 years ago
•
|
||
Sorry Pascal, I mid-aired the tracking flag away.
| Assignee | ||
Comment 6•6 years ago
|
||
| Assignee | ||
Comment 7•6 years ago
|
||
Updated•6 years ago
|
| Assignee | ||
Comment 8•6 years ago
|
||
| Assignee | ||
Comment 9•6 years ago
|
||
Depends on D27600
| Assignee | ||
Comment 10•6 years ago
|
||
GetBuffer() would always return null here.
Depends on D27601
| Assignee | ||
Comment 11•6 years ago
|
||
Depends on D27603
Updated•6 years ago
|
Updated•6 years ago
|
Comment 12•6 years ago
|
||
| Assignee | ||
Comment 13•6 years ago
|
||
Try push before fuzz adjustment: https://treeherder.mozilla.org/#/jobs?repo=try&revision=96ac78ab8543f5e827d58559f84882657987f88b
Comment 15•6 years ago
|
||
| bugherder | ||
https://hg.mozilla.org/mozilla-central/rev/cf3fbdaa46b9
https://hg.mozilla.org/mozilla-central/rev/d5ac9681d3ce
https://hg.mozilla.org/mozilla-central/rev/4ab1a110e5d5
https://hg.mozilla.org/mozilla-central/rev/185e608c3852
| Assignee | ||
Comment 16•6 years ago
|
||
Comment on attachment 9058424 [details]
Bug 1544478 - Respect SharedRGBImage's stride during YUV->RGBA conversion. r?mattwoodrow
Beta/Release Uplift Approval Request
- User impact if declined: Some videos (WebM with alpha) will be displayed with a skew on macOS
- Is this code covered by automated tests?: No
- Has the fix been verified in Nightly?: Yes
- Needs manual test from QE?: No
- If yes, steps to reproduce:
- List of other uplifts needed: None
- Risk to taking this patch: Low
- Why is the change risky/not risky? (and alternatives if risky): The fix is small and tightly-scoped, and applies to code which is only run for a certain type of video.
- String changes made/needed:
| Assignee | ||
Updated•6 years ago
|
Comment 17•6 years ago
|
||
Comment on attachment 9058424 [details]
Bug 1544478 - Respect SharedRGBImage's stride during YUV->RGBA conversion. r?mattwoodrow
The regression is very visible for a subset of our users and the patch looks safe and has tests. There is no request for manual QA while we have STR in comment #0, so let's ask for QA after landing on beta. Uplift accepted for 67 beta 13, thanks.
Updated•6 years ago
|
Comment 18•6 years ago
|
||
| bugherder uplift | ||
Updated•6 years ago
|
Updated•6 years ago
|
Updated•6 years ago
|
Updated•6 years ago
|
Comment 19•6 years ago
|
||
Reproduced the issue on 67.0b12 on Mac 10.13.6
Verified as fixed on Mac 10.13.6 on 67.0b13 and 68.0a1 20190424095359.
Updated•3 years ago
|
Description
•