Closed
Bug 1406439
Opened 7 years ago
Closed 7 years ago
[meta] Blocking video issues in 57
Categories
(Core :: Graphics, defect, P2)
Core
Graphics
Tracking
()
RESOLVED
FIXED
People
(Reporter: milan, Assigned: milan)
References
Details
(Whiteboard: [gfx-noted])
There are reports of video related graphics issues "57 is great except for video" type of thing (e.g., bug 1403091 comment 3). This meta bug is trying to group all the reports, which often don't contain all the information we need, in hope of being able to figure out the reasons in aggregate.
Assignee | ||
Comment 1•7 years ago
|
||
Bug 1393392 removed blocking of a number of devices for video decoding - it mentions telemetry; asked for the telemetry results in that bug.
Jean-Yves, you have the information from Nvidia about Tesla and decoding - I can't find the bug for blocking those out, is there one?
Assignee | ||
Comment 2•7 years ago
|
||
[Tracking Requested - why for this release]: It may be strange to track a meta bug, but our evidence is currently spotty and circumstantial, so until we have something better, track this one.
status-firefox57:
--- → affected
tracking-firefox57:
--- → ?
Assignee | ||
Updated•7 years ago
|
Priority: -- → P1
Whiteboard: [gfx-noted]
Assignee | ||
Updated•7 years ago
|
Assignee: nobody → milan
Assignee | ||
Updated•7 years ago
|
Comment 3•7 years ago
|
||
(In reply to Milan Sreckovic [:milan] from comment #2)
> [Tracking Requested - why for this release]: It may be strange to track a
> meta bug, but our evidence is currently spotty and circumstantial, so until
> we have something better, track this one.
Milan: Do you think these are issues that are of 57 release blocking quality, or ones that would be nice to fix? Or maybe we don't know yet.
Flags: needinfo?(milan)
Assignee | ||
Comment 4•7 years ago
|
||
I'm afraid there may be blockers; bug 1405110, bug 1404456, bug 1405838 graphs all look either large, or scary slopes, with more older Windows in there, and those could explode on release.
Flags: needinfo?(milan)
Comment 5•7 years ago
|
||
(In reply to Milan Sreckovic [:milan] from comment #1)
> Bug 1393392 removed blocking of a number of devices for video decoding - it
> mentions telemetry; asked for the telemetry results in that bug.
>
> Jean-Yves, you have the information from Nvidia about Tesla and decoding - I
> can't find the bug for blocking those out, is there one?
The information about Nvidia and tesla based cards was that they didn't handle nv12 surface. It is now disabled for those starting in 56.
There were other issues with old amd cards, also reported to not handle nv12 surfaces properly, and they have been forced to use rgb too.
For Intel, there's been no such report. And for now they are using nv12.
The problem with those Intel is thst they were crashing when using RGB!
Flags: needinfo?(jyavenard)
Comment 6•7 years ago
|
||
(In reply to Milan Sreckovic [:milan] from comment #1)
> Bug 1393392 removed blocking of a number of devices for video decoding - it
> mentions telemetry; asked for the telemetry results in that bug.
>
> Jean-Yves, you have the information from Nvidia about Tesla and decoding - I
> can't find the bug for blocking those out, is there one?
Sorry, forgot to answer that last question. The use of nv12 surfaces with nvidia Tesla was blocked in bug 1352016
Bumping this up to blocking 57.
Assignee | ||
Comment 9•7 years ago
|
||
Anthony, are we in good enough shape with video to make this meta a non-blocker?
Flags: needinfo?(ajones)
(In reply to Milan Sreckovic [:milan] from comment #9)
> Anthony, are we in good enough shape with video to make this meta a
> non-blocker?
Yes. I think we're in good enough shape. The crashes are all sufficiently low volume. I'll let you worry about the more general and non-video specific issues.
Assignee | ||
Comment 11•7 years ago
|
||
Going to resolve this "blocker meta" as fixed.
Status: NEW → RESOLVED
Closed: 7 years ago
Priority: P1 → P2
Resolution: --- → FIXED
Summary: [meta] Video issues in 57 → [meta] Blocking video issues in 57
Updated•7 years ago
|
You need to log in
before you can comment on or make changes to this bug.
Description
•