Skip to content

feat: Add Chromium startup-trimming flags to speed up rendering - #743

Open
rusudorin wants to merge 1 commit into
fatihak:mainfrom
rusudorin:perf/chromium-startup-flags
Open

feat: Add Chromium startup-trimming flags to speed up rendering#743
rusudorin wants to merge 1 commit into
fatihak:mainfrom
rusudorin:perf/chromium-startup-flags

Conversation

@rusudorin

Copy link
Copy Markdown
Contributor

Chromium cold-start dominates render time on low-resource devices like the Pi Zero. Add flags that disable first-run setup, background networking, sync, default apps, component updates and unneeded features to reduce browser launch overhead for one-shot screenshots.

Chromium cold-start dominates render time on low-resource devices like
the Pi Zero. Add flags that disable first-run setup, background
networking, sync, default apps, component updates and unneeded features
to reduce browser launch overhead for one-shot screenshots.

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Copilot AI lite review requested due to automatic review settings August 16, 2026 12:51

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.

Pull request overview

This PR reduces Chromium cold-start overhead for one-shot, headless screenshots (notably on constrained devices like a Raspberry Pi Zero) by adding startup-trimming CLI flags to the screenshot invocation path.

Changes:

  • Adds Chromium flags to skip first-run/default-browser prompts and reduce background networking/sync/default-app/component-update work.
  • Disables specific Chromium features (Translate, BackForwardCache) to further minimize startup work for screenshot-only usage.

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

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