Skip to content

fix(web): isolate CEF cache per renderer process - #157

Merged
hypengw merged 1 commit into
waywallen:mainfrom
MR-kartoshki:fix/weweb-unique-cef-cache
Oct 15, 2026
Merged

hypengw merged 1 commit into
waywallen:mainfrom
MR-kartoshki:fix/weweb-unique-cef-cache

Conversation

@MR-kartoshki

Copy link
Copy Markdown
Contributor

Give each web renderer process its own CEF root cache directory.

When duplicate renderers are enabled, multiple waywallen-weweb-renderer processes for the same Wallpaper Engine web wallpaper currently derive the same CEF cache path from the Workshop ID. The first renderer starts successfully, while the second can fail during CefInitialize because Chromium treats the shared profile as an existing browser session.

This appends the renderer process ID to the cache path so each renderer gets an independent CEF root cache.

Reproduction of the bug

  1. Enable duplicate renderers.
  2. Apply the same web wallpaper to multiple displays.
  3. The first renderer starts successfully.
  4. The second renderer logs:
    • Opening in existing browser session.
    • weweb: CefInitialize failed
    • BrowserHost::Init failed

Tested

Built using the project's official scripts/build_waywallen_plugin.sh packaging flow and tested with the Waywallen Flatpak.

With this change, multiple web renderer processes for the same wallpaper start successfully and coexist without the CEF initialization failure.

@hypengw
hypengw merged commit d906a69 into waywallen:main Oct 15, 2026
@MR-kartoshki
MR-kartoshki deleted the fix/weweb-unique-cef-cache branch October 19, 2026 15:01
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants