Skip to content

Conversation

@rgarcia
Copy link
Contributor

@rgarcia rgarcia commented Jan 17, 2026

Summary

  • Update --use-angle to --use-angle=swiftshader for software-based GPU rendering
  • Update --use-gl=disabled to --use-gl=egl-angle to use ANGLE's EGL backend

Test plan

  • Verify headless chromium launches successfully with new flags
  • Test screenshot/PDF generation works correctly

🤖 Generated with Claude Code


Note

Updates headless Chromium flags and hardens devtools proxy tests.

  • images/chromium-headless: switch to --use-angle=swiftshader, --use-gl=angle, and add --hide-crash-restore-bubble in wrapper.sh
  • server/lib/devtoolsproxy: improve test robustness and diagnostics (testLogWriter, safer teardown, extra logging, log dump on failures) for TestUpstreamManagerDetectsChromiumAndRestart

Written by Cursor Bugbot for commit d312592. This will update automatically on new commits. Configure here.

Update GPU rendering flags to use software rendering via SwiftShader
with ANGLE's EGL backend for more consistent headless browser behavior.

Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
rgarcia and others added 2 commits January 16, 2026 19:51
Suppresses the crash restore bubble UI in headless Chromium.

Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
…tart

When this test fails, it now logs:
- The Chromium command and args being executed
- The PID of the Chromium process
- The UpstreamManager's debug logs
- The full contents of the Chromium log file on failure

This helps debug CI failures where the test times out waiting for
the DevTools WebSocket URL to appear.
Copy link

@cursor cursor bot left a comment

Choose a reason for hiding this comment

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

Cursor Bugbot has reviewed your changes and found 1 potential issue.

Bugbot Autofix is OFF. To automatically fix reported issues with Cloud Agents, enable Autofix in the Cursor dashboard.

@masnwilliams
Copy link

quick question on the --use-gl=egl-angle flag - chromium docs list the valid values as desktop, egl, angle, and swiftshader, and the recommended combo for SwANGLE is --use-gl=angle --use-angle=swiftshader. is egl-angle a newer variant I'm not finding in the docs, or should this be --use-gl=angle?

(the bugbot comment on #992 flagged something similar - just want to make sure we don't silently fall back to default GL rendering)

Copy link

@masnwilliams masnwilliams left a comment

Choose a reason for hiding this comment

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

lgtm, just check out the comments re: the --use-gl flag value and the test logger potential panic

Address PR review comments:

1. Fix --use-gl flag: change from invalid 'egl-angle' to valid 'angle'.
   The 'egl-angle' value is an internal implementation name, not a valid
   command line flag. Valid values are: egl, angle, mock, stub, disabled.
   The correct SwANGLE config is --use-gl=angle --use-angle=swiftshader.

2. Fix potential panic in TestUpstreamManagerDetectsChromiumAndRestart:
   The testLogWriter now uses atomic.Bool to track when the test is done.
   After canceling the context, we stop the log writer before the test
   returns to prevent panics from the background tail goroutine logging
   after test completion.
@rgarcia rgarcia merged commit ca3fe93 into main Jan 17, 2026
5 checks passed
@rgarcia rgarcia deleted the use-swiftshader-angle-flags branch January 17, 2026 20:46
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