Closed
Bug 848936
Opened 12 years ago
Closed 12 years ago
Various SVG ref test failures on Windows 8
Categories
(Core :: Graphics, defect)
Tracking
()
RESOLVED
FIXED
mozilla22
People
(Reporter: jimm, Assigned: jimm)
References
(Blocks 1 open bug)
Details
Attachments
(2 files)
12.08 KB,
image/png
|
Details | |
11.93 KB,
patch
|
roc
:
review+
|
Details | Diff | Splinter Review |
The data images don't look different via a visual inspection.
Guessing this is graphics/d2d related.
standalone--auto-auto--pct-pct.svg | max difference: 1, differing pixels: 392
standalone--auto-pct--pct-0.svg | max difference: 1, differing pixels: 392
standalone--auto-pct--pct-pct.svg | max difference: 1, differing pixels: 392
standalone--auto-pct--pct-px.svg | max difference: 1, differing pixels: 392
standalone--auto-pct--px-px.svg | max difference: 1, differing pixels: 979
standalone--pct-auto--0-pct.svg | max difference: 1, differing pixels: 392
standalone--pct-auto--pct-pct.svg | max difference: 1, differing pixels: 392
standalone--pct-auto--px-pct.svg | max difference: 1, differing pixels: 392
standalone--pct-pct--0-0.svg | max difference: 1, differing pixels: 392
standalone--pct-pct--0-pct.svg | max difference: 1, differing pixels: 392
standalone--pct-pct--0-px.svg | max difference: 1, differing pixels: 392
standalone--pct-pct--pct-0.svg | max difference: 1, differing pixels: 392
standalone--pct-pct--pct-pct.svg | max difference: 1, differing pixels: 392
standalone--pct-pct--pct-px.svg | max difference: 1, differing pixels: 392
standalone--pct-pct--px-0.svg | max difference: 1, differing pixels: 392
standalone--pct-pct--px-pct.svg | max difference: 1, differing pixels: 392
standalone--pct-pct--px-px.svg | max difference: 1, differing pixels: 392
feColorMatrix-1.svg | max difference: 1, differing pixels: 6400
feColorMatrix-2.svg | max difference: 1, differing pixels: 10000
feComposite-1.svg | max difference: 1, differing pixels: 9600
feComposite-2.svg | max difference: 1, differing pixels: 10000
feFlood-1.svg | max difference: 1, differing pixels: 6400
feFlood-2.svg | max difference: 1, differing pixels: 250000
clipPath-and-shape-rendering-01.svg | max difference: 1, differing pixels: 3
dynamic-filter-contents-01a.svg | max difference: 1, differing pixels: 10000
dynamic-filter-contents-01b.svg | max difference: 1, differing pixels: 10000
mask-type-01.svg | max difference: 1, differing pixels: 6400
mask-type-02.svg | max difference: 1, differing pixels: 6400
mask-type-03.svg | max difference: 1, differing pixels: 6400
mask-type-04.svg | max difference: 1, differing pixels: 6400
opacity-and-gradient-02.svg | max difference: 1, differing pixels: 200000
![]() |
Assignee | |
Updated•12 years ago
|
Assignee: nobody → jmathies
![]() |
Assignee | |
Comment 1•12 years ago
|
||
Looking specifically at opacity-and-gradient-02.svg, the middle color bar has rgb values of 128,128,0. In the live svg image the resulting image surface we compare has a middle band that transitions half way through from 128,128,0 to 128,127,0. Hence the failure.
![]() |
Assignee | |
Comment 2•12 years ago
|
||
![]() |
Assignee | |
Comment 3•12 years ago
|
||
cc'ing a couple gfx folks. Joe, Jeff, any suggestions on the best place in the code to look for the cause of something like this? Our svg ref tests are failing pretty hard on Win8. The cause appears to be minor color shifting in the initial canvas rendering or in the resulting image surface we do the comparison with.
![]() |
Assignee | |
Comment 4•12 years ago
|
||
Setting layers.acceleration.disabled to true fixes the failure.
![]() |
Assignee | |
Comment 5•12 years ago
|
||
The drivers we have on these are one rev out out of date. I'm not sure if a bad driver could cause something like this though.
Card name: NVIDIA GeForce GT 430
Manufacturer: NVIDIA
Chip type: GeForce GT 430
DAC type: Integrated RAMDAC
Device Type: Full Device
Device Key: Enum\PCI\VEN_10DE&DEV_0DE1&SUBSYS_14303842&REV_A1
Display Memory: 4050 MB
Dedicated Memory: 978 MB
Shared Memory: 3071 MB
Current Mode: 1600 x 1200 (32 bit) (60Hz)
Driver Name: nvd3dumx.dll,nvwgf2umx.dll,nvwgf2umx.dll,nvd3dum,nvwgf2um,nvwgf2um
Driver File Version: 9.18.0013.1090 (English)
Driver Version: 9.18.13.1090
DDI Version: 11
Feature Levels: 11.0,10.1,10.0,9.3,9.2,9.1
Driver Model: WDDM 1.2
Graphics Preemption: DMA
Compute Preemption: DMA
Driver Attributes: Final Retail
Driver Date/Size: 12/29/2012 02:34:47, 18054312 bytes
![]() |
Assignee | |
Comment 6•12 years ago
|
||
Bas, any ideas here as to what might be causing the color shifting in these tests? We could try upgrading the driver if you think that might help. I'm curious if we've run into this kind of problem before with direct2d.
Flags: needinfo?(bas)
![]() |
Assignee | |
Updated•12 years ago
|
Assignee: jmathies → nobody
![]() |
Assignee | |
Comment 8•12 years ago
|
||
<jimm> Bas: do you have any ideas on bug 848936? that's holding up getting win8 desktop running on mc.
<Bas> jimm: Those fail for me locally on m-c too.
<Bas> jimm: Our tinderbox test machines are the magical machines where reftests pass, I've never seen them pass with D2D on any other hardware :)
<jimm> Bas: what do you think we should do? fuzzy the heck out of the tests, disable them, ..?
<Bas> jimm: Fuzzy them, yes. A subpixel difference of 1 max is really always innocent when it comes to how we do reftests.
<Bas> jimm: fwiw, I think they're due to GPU rounding not being IEEE 754 compliant
I will work up a patch here and in bug 850457.
![]() |
Assignee | |
Comment 9•12 years ago
|
||
annotation for various tests for the new testing hardware. on the few that failed hard, I just skipped.
Assignee: nobody → jmathies
Attachment #724643 -
Flags: review?(roc)
Comment on attachment 724643 [details] [diff] [review]
patch
Review of attachment 724643 [details] [diff] [review]:
-----------------------------------------------------------------
Please file bug(s) for the tests that fail completely.
Attachment #724643 -
Flags: review?(roc) → review+
![]() |
Assignee | |
Comment 11•12 years ago
|
||
Comment 12•12 years ago
|
||
Status: NEW → RESOLVED
Closed: 12 years ago
Resolution: --- → FIXED
Target Milestone: --- → mozilla22
You need to log in
before you can comment on or make changes to this bug.
Description
•