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
It may be possible to avoid it, but a very few wallpapers on the Workshop aren't stable. Which one were you using?
The other issue I don't really understand yet, but there is a 600MB+ web wallpaper which seems to leak resources and crash.
But anyway, yeah, if you have any .mdmps they might help. I suspect the graphics driver just crashed or something though.
One .mdmp shows that the graphics device died, so the message appeared a second time because Chromium attempted to restart the render process, which apparently failed though.
It might have logged some graphics related error in this file: C:\Program Files (x86)\Steam\steamapps\common\wallpaper_engine\bin\debug.log could you share it too?
Both are basically using the same files, so not sure if it's just coincidence or if it means something.
The log looks like it was calling the graphics device with some invalid state after it was restored (glCopySubTextureCHROMIUM: source texture has no level 0) that could bug the driver, but I would expect it to log a TDR event in the event viewer, though you said there wasn't anything.
Do you know which renderer Chromium uses for you? Would probably be Dx11 if your card supports it and the command line option was empty otherwise.
Here are screenshots of the event viewer at the time of the crash:
[APPLICATION] https://gyazo.com/8df1451e44181915457090f46e86a021
[SYSTEM] https://gyazo.com/e7d654b710abdfc6962f7324da7656a7
The first crash occured at 16:53, the second at 17:46.
Do you have any idea how I might be able to reproduce it? I've updated CEF to the latest version now and disabled the watchdog by default. So if there was anything wrong there, perhaps it's rectified now.
I guess it might have caused the first one somehow, otherwise it would be quite a coincidence I guess? The second one likely came from the buggy watchdog, so having that disabled may take care of it.