Preliminary blacklisted features can be used uninitialized |
||
Issue descriptionThe issue is the following: Looking at: https://cs.chromium.org/chromium/src/content/browser/gpu/gpu_data_manager_impl_private.cc?type=cs&l=1203 UpdateGpuInfo(gpu_info); UpdateGpuSwitchingManager(gpu_info); UpdatePreliminaryBlacklistedFeatures(); In this case, GpuAccessAllowed() can get called here: UpdateGpuInfo() -> UpdateGpuInfoHelper() -> UpdateBlacklistedFeatures() -> EnableSwiftShaderIfNecessary() -> GpuAccessAllowed() In this scenario, GpuAccessAllowed() returns false here: https://cs.chromium.org/chromium/src/content/browser/gpu/gpu_data_manager_impl_private.cc?type=cs&l=388 The reason it returns false is that UpdatePreliminaryBlacklistedFeatures() hasn't been called yet.
,
Aug 27
This should probably have been fixed when the cl landed. |
||
►
Sign in to add a comment |
||
Comment 1 by bugdroid1@chromium.org
, Mar 2 2017