Skip to content

perf: limit embedded browser renderer processes - #274

Open
livvaa wants to merge 1 commit into
GermanCoding:mainfrom
livvaa:contrib/cef-renderer-limit
Open

perf: limit embedded browser renderer processes#274
livvaa wants to merge 1 commit into
GermanCoding:mainfrom
livvaa:contrib/cef-renderer-limit

Conversation

@livvaa

@livvaa livvaa commented Aug 24, 2026

Copy link
Copy Markdown

Summary

  • Limits Chromium to one renderer process for SyncTrayzor's single trusted local page.
  • Avoids keeping an unnecessary spare renderer process and reduces idle memory usage.

Testing

  • dotnet test src -c Release --no-restore
  • 58 tests passed.

Copilot AI lite review requested due to automatic review settings August 24, 2026 04:28

Copilot AI left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🟢 Approval recommended

The change is small and low-risk, with only a minor documentation wording concern noted.

Pull request overview

This PR reduces idle memory usage in SyncTrayzor’s embedded CefSharp browser by limiting Chromium’s renderer process count, which aligns with the app’s single embedded browser usage.

Changes:

  • Adds a Chromium command-line switch to cap renderer processes at 1.
  • Minor formatting/whitespace adjustment at the end of ViewerViewModel.cs.
File summaries
File Description
src/SyncTrayzor/Pages/ViewerViewModel.cs Adds renderer-process-limit=1 to CefSharp initialization to reduce idle renderer overhead.
Review details
  • Files reviewed: 1/1 changed files
  • Comments generated: 1
  • Review effort level: Lite

💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.

Comment on lines +163 to +164
// SyncTrayzor hosts a single trusted local page. Chromium otherwise keeps a spare renderer
// around, which adds roughly 50 MiB of idle memory without benefiting this single-view app.
@GermanCoding

Copy link
Copy Markdown
Owner

I'll have to give this some more testing, but on first look this looks good.

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.

3 participants