Swiftshader use may still be requested even when the feature is disabled
Reported by
ptwo...@vewd.com,
Dec 12 2017
|
||||||
Issue descriptionUserAgent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/62.0.3202.94 Safari/537.36 Steps to reproduce the problem: 1. Build chromium with swiftshader disabled (enable_switshader=false) 2. Try to run any TC that would try to fall back to software GL implementation What is the expected behavior? Software GL implementation requested is not kGLImplementationSwiftShaderGL What went wrong? Chromium still expects kGLImplementationSwiftShaderGL to be the software GL implementation even though it's disabled. Did this work before? N/A Chrome version: 65.0.3293.0 Channel: n/a OS Version: 4.12.12 Flash Version:
,
Dec 12 2017
,
Dec 12 2017
,
Dec 13 2017
The issue seems to be out of TE-scope as it is related to Swiftshader(clusterfuzz). Hence, adding label TE-NeedsTriageHelp for further investigation from dev team. Thanks...!!
,
Dec 15 2017
Assigning sugoi to review the patch.
,
Sep 6
The related patch has been abandoned as obsolete. Also closing this issue as obsolete. Please feel free to reopen if there's still an issue here. |
||||||
►
Sign in to add a comment |
||||||
Comment 1 by ptwo...@vewd.com
, Dec 12 2017