InProcessCommandBuffer doesn't respect exit_on_context_lost GPU driver workaround |
|
Issue descriptionAs of right now InProcessCommandBuffer doesn't check exit_on_context_lost GPU driver bug workaround on context loss. For IPC command buffers the check happens at [1]. I think this also means that losing all contexts if one context is lost at [2] doesn't happen. The exit_on_context_lost driver workaround is enabled always on Windows/Linux and for Mali 400/450 GPUs on Android. This likely needs to be fixed but I'm not sure what the impact is. OOP-D is enabled for 50% of stable users on Windows/Linux users. I haven't seen any bugs resulting from skipping this driver workaround (although that doesn't mean there aren't any). OOP-D is also enabled for 10% of stable users on Android. I haven't been following Android as closely. [1] https://cs.chromium.org/chromium/src/gpu/ipc/service/gpu_channel_manager.cc?l=461&rcl=89140af1a339c40bc2e1398939df41e3729d97c7 [2] https://cs.chromium.org/chromium/src/gpu/ipc/service/gpu_channel_manager.cc?l=468&rcl=89140af1a339c40bc2e1398939df41e3729d97c7 |
|
►
Sign in to add a comment |
|