Install Steam
login
|
language
简体中文 (Simplified Chinese)
繁體中文 (Traditional Chinese)
日本語 (Japanese)
한국어 (Korean)
ไทย (Thai)
Български (Bulgarian)
Čeština (Czech)
Dansk (Danish)
Deutsch (German)
Español - España (Spanish - Spain)
Español - Latinoamérica (Spanish - Latin America)
Ελληνικά (Greek)
Français (French)
Italiano (Italian)
Bahasa Indonesia (Indonesian)
Magyar (Hungarian)
Nederlands (Dutch)
Norsk (Norwegian)
Polski (Polish)
Português (Portuguese - Portugal)
Português - Brasil (Portuguese - Brazil)
Română (Romanian)
Русский (Russian)
Suomi (Finnish)
Svenska (Swedish)
Türkçe (Turkish)
Tiếng Việt (Vietnamese)
Українська (Ukrainian)
Report a translation problem
Moving to a new version of CEF and Chromium doesn't help.
The problem is the Steam Client doesn't respond to the driver reset signals that Windows sends to the process's main window loop and doesn't forward those to the embedded Chromium instance, which - as it is embedded, and doesn't have its own main window loop - can't do that automatically.
This is the same reason Chromium in the Steam client keeps eating RAM and CPU even when the window is minimized or when an exclusive fullscreen mode game is active. Chromium itself doesn't have a window. It doesn't know when it does and does not have foreground focus. It does not know when it should and should not bother updating rendered content because users won't be able to see it or interact with it. It has to be told by the owning process.
CEF handles that to some degree. But far from all of it.
This is the same reason the Steam Client randomly black-screens for some people.
Chromium's renderer is blazing fast because Google tries to eek every bit of performance out of it that they can with a myriad of dangerous optimizations that more often than not backfire on particular driver versions that have bad interplay with them.
When that happens the video driver partially hangs and is issued what is called a partial reset. Resources belonging to the process that caused the crash are invalidated when this reset happens and the process is sent a signal that the old device was removed and a new one was added.
Chromium normally responds to that by killing its old renderer instance and starting a new one. Which happens so fast most users won't even notice.
But of course; the Steam Client - as I mentioned earlier - doesn't process those window messages properly and doesn't forward them to Chromium. So it remains stuck with broken rendering resources and the user is left staring at a black screen.
And that's why I think an upgrade to the latest version of Chromium should bring much higher stability. New version = new, updated code and support for new graphics cards including current blacklists and whitelists. Will not fix all the problems like memory hog, but IMHO stability should. How old is the current CEF used on Steam? 2-3 years? Whereas why Steam doesn't use the late 2022 version 109 - so, this question should not be put to me (old Linux systems compatibility, especially those based on *buntu branch?).
Its normal. CEF poorly tolerates GPU driver reset. And not only CEF. It is best practice to close all applications on the screen before updating the drivers.