gl_tests DirectCompositionPixelTest subtests such as .SoftwareVideoSwapchain fail for D3D11 devices with feature level 10_1 |
||
Issue description
Chrome Version: master
OS: Win10
Gpu: NVIDIA Geforce 210
What steps will reproduce the problem?
(1) gl_tests --gtest_filter=DirectComposition*
What is the expected result?
pass
What happens instead?
[17:29:32] [Step 4/6] [----------] 4 tests from DirectCompositionPixelTest
[17:29:32] [Step 4/6] [ RUN ] DirectCompositionPixelTest.DCLayersEnabled
[17:29:33] [Step 4/6] [ OK ] DirectCompositionPixelTest.DCLayersEnabled (1056 ms)
[17:29:33] [Step 4/6] [ RUN ] DirectCompositionPixelTest.DCLayersDisabled
[17:29:34] [Step 4/6] [ OK ] DirectCompositionPixelTest.DCLayersDisabled (1080 ms)
[17:29:34] [Step 4/6] [ RUN ] DirectCompositionPixelTest.SoftwareVideoSwapchain
[17:29:35] [Step 4/6] ../../gpu/ipc/service/direct_composition_surface_win_unittest.cc(643): error: Value of: AreColorsSimilar(expected_color, actual_color)
[17:29:35] [Step 4/6] Actual: false
[17:29:35] [Step 4/6] Expected: true
[17:29:35] [Step 4/6] Expected ffffb7ff Actual ffffaaff
[17:29:35] [Step 4/6] [ FAILED ] DirectCompositionPixelTest.SoftwareVideoSwapchain (1084 ms)
[17:29:35] [Step 4/6] [ RUN ] DirectCompositionPixelTest.VideoHandleSwapchain
[17:29:36] [Step 4/6] ../../gpu/ipc/service/direct_composition_surface_win_unittest.cc(694): error: Value of: AreColorsSimilar(expected_color, actual_color)
[17:29:36] [Step 4/6] Actual: false
[17:29:36] [Step 4/6] Expected: true
[17:29:36] [Step 4/6] Expected ffe190eb Actual ffd789e0
[17:29:36] [Step 4/6] [ FAILED ] DirectCompositionPixelTest.VideoHandleSwapchain (1080 ms)
[17:29:36] [Step 4/6] [----------] 4 tests from DirectCompositionPixelTest (4302 ms total)
[17:29:36] [Step 4/6]
[17:29:36] [Step 4/6] [----------] 2 tests from DirectCompositionVideoPixelTest
[17:29:36] [Step 4/6] [ RUN ] DirectCompositionVideoPixelTest.BT601
[17:29:37] [Step 4/6] [ OK ] DirectCompositionVideoPixelTest.BT601 (1081 ms)
[17:29:37] [Step 4/6] [ RUN ] DirectCompositionVideoPixelTest.BT709
[17:29:38] [Step 4/6] ../../gpu/ipc/service/direct_composition_surface_win_unittest.cc(559): error: Value of: AreColorsSimilar(expected_color, actual_color)
[17:29:38] [Step 4/6] Actual: false
[17:29:38] [Step 4/6] Expected: true
[17:29:38] [Step 4/6] Expected ffe190eb Actual ffd789e0
[17:29:38] [Step 4/6] [ FAILED ] DirectCompositionVideoPixelTest.BT709 (1081 ms)
[17:29:38] [Step 4/6] [----------] 2 tests from DirectCompositionVideoPixelTest (2163 ms total)
[17:29:38] [Step 4/6]
[17:29:38] [Step 4/6] [----------] Global test environment tear-down
[17:29:38] [Step 4/6] [==========] 10 tests from 3 test cases ran. (6609 ms total)
[17:29:38] [Step 4/6] [ PASSED ] 7 tests.
[17:29:38] [Step 4/6] [ FAILED ] 3 tests, listed below:
[17:29:38] [Step 4/6] [ FAILED ] DirectCompositionPixelTest.SoftwareVideoSwapchain
[17:29:38] [Step 4/6] [ FAILED ] DirectCompositionPixelTest.VideoHandleSwapchain
[17:29:38] [Step 4/6] [ FAILED ] DirectCompositionVideoPixelTest.BT709
[17:29:38] [Step 4/6]
[17:29:38] [Step 4/6] 3 FAILED TESTS
dxdiag of the device:
---------------
Display Devices
---------------
Card name: NVIDIA GeForce 210
Manufacturer: NVIDIA
Chip type: GeForce 210
DAC type: Integrated RAMDAC
Device Type: Full Device
Device Key: Enum\PCI\VEN_10DE&DEV_0A65&SUBSYS_83C71043&REV_A2
Device Status: 0180200A [DN_DRIVER_LOADED|DN_STARTED|DN_DISABLEABLE|DN_NT_ENUMERATOR|DN_NT_DRIVER]
Device Problem Code: No Problem
Driver Problem Code: Unknown
Display Memory: 4043 MB
Dedicated Memory: 459 MB
Shared Memory: 3583 MB
Current Mode: 1920 x 1080 (32 bit) (32Hz)
HDR Support: Unknown
Display Topology: Unknown
Display Color Space: DXGI_COLOR_SPACE_RGB_FULL_G22_NONE_P709
Color Primaries: Red(0.000500,0.000500), Green(0.000500,0.000500), Blue(0.000500,0.000500), White Point(0.000500,0.000500)
Display Luminance: Min Luminance = 0.000000, Max Luminance = 0.000000, MaxFullFrameLuminance = 0.000000
Driver Name: nvd3dumx.dll,nvwgf2umx.dll,nvwgf2umx.dll
Driver File Version: 9.18.0013.4174 (English)
Driver Version: 9.18.13.4174
DDI Version: 11.1
Feature Levels: 10_1,10_0,9_3,9_2,9_1
Driver Model: WDDM 1.2
Graphics Preemption: DMA
Compute Preemption: DMA
Miracast: Not Supported
Hybrid Graphics GPU: Not Applicable
Power P-states: Not Applicable
Driver Attributes: Final Retail
Driver Date/Size: 6/29/2015 3:00:00 AM, 17559432 bytes
WHQL Logo'd: Yes
WHQL Date Stamp: Unknown
Device Identifier: {D7B71E3E-4925-11CF-BD63-CAA31FC2C435}
Vendor ID: 0x10DE
Device ID: 0x0A65
SubSys ID: 0x83C71043
Revision ID: 0x00A2
Driver Strong Name: oem12.inf:0f066de3ee1b1cfd:Section004:9.18.13.4174:pci\ven_10de&dev_0a65
Rank Of Driver: 00DA2001
Video Accel: Unknown
DXVA2 Modes: DXVA2_ModeMPEG2_IDCT DXVA2_ModeMPEG2_VLD DXVA2_ModeVC1_D2010 DXVA2_ModeVC1_VLD DXVA2_ModeVC1_IDCT DXVA2_ModeWMV9_IDCT DXVA2_ModeH264_VLD_Stereo_Progressive_NoFGT DXVA2_ModeH264_VLD_Stereo_NoFGT DXVA2_ModeH264_VLD_NoFGT DXVA2_ModeMPEG4pt2_VLD_Simple DXVA2_ModeMPEG4pt2_VLD_AdvSimple_NoGMC
Deinterlace Caps: n/a
D3D9 Overlay: Supported
DXVA-HD: Supported
DDraw Status: Not Available
D3D Status: Enabled
AGP Status: Not Available
MPO MaxPlanes: 1
MPO Caps: Not Supported
MPO Stretch: Not Supported
MPO Media Hints: Not Supported
MPO Formats: Not Supported
PanelFitter Caps: Not Supported
PanelFitter Stretch: Not Supported
No big deal, just asking whether the failure is of interest or not
,
Jun 5 2018
Let me see if I can repro locally since I also have a NVidia GPU. Likely some settings got wrong value in testing.
,
Jun 5 2018
I can't reproduce on my side. Looking at the failing test, it seems like your driver fails to handle BT.709 videos in SwapChains. We ran into similar issues on some Intel drivers, the colors are slightly off. This is (I think) the first time we ran into that on NVidia driver. Can you check some videos in Chrome on that machine? If the colors are dramatically wrong, then probably we need to fix the driver issue. Otherwise if the difference is not for human eyes to tell, I think we don't need to do anything.
,
Jun 5 2018
We have a code path to fall back to BT.601, but per discussion with sunnyps, it's really not something we want to do because that means extra processing between source video frame and output, and we try to optimize our video rendering path by removing all unnecessary extra processing. |
||
►
Sign in to add a comment |
||
Comment 1 by kbr@chromium.org
, Jun 5 2018