Skip to content

fix(cef): downgrade gstcefsrc to CEF 126 (Alloy runtime) to avoid Mem…#505

Merged
srperens merged 1 commit intomainfrom
fix/cef-126-alloy-runtime
Apr 17, 2026
Merged

fix(cef): downgrade gstcefsrc to CEF 126 (Alloy runtime) to avoid Mem…#505
srperens merged 1 commit intomainfrom
fix/cef-126-alloy-runtime

Conversation

@srperens
Copy link
Copy Markdown
Collaborator

…oryInfra SIGILL

CEF 127+ switched to Chrome runtime by default, introducing a MemoryInfra / PartitionAlloc CHECK() failure (SIGILL, exit 132) that crashes long-running cefsrc processes intermittently. No upstream fix exists. CEF 128 removed the Alloy bootstrap entirely.

Pin the build to:

  • CEF 126.2.18+g3647d39+chromium-126.0.6478.183 (last stable Alloy-default)
  • gstcefsrc 0e470f51fd (last master commit defaulting to CEF 122, compatible with the CEF 126 ABI)

Changes:

  • docker/gstcefsrc/Dockerfile: bump default CEF_VERSION, add GSTCEFSRC_REF arg, switch clone from --depth 1 to init/fetch/checkout to support arbitrary SHAs.
  • .github/workflows/build-gstcefsrc.yml: update defaults, add gstcefsrc_ref workflow_dispatch input, wire through as --build-arg.
  • docker/strom-full/entrypoint.sh: update comment — Chrome-runtime-specific flags are no-ops on Alloy but kept as defense-in-depth.
  • docs/CEF_SIGILL_CRASH.md: new "Downgrade to CEF 126" section documenting rationale and pinning locations; old flag-based fix retained as legacy.

Note: docker/strom-full/Dockerfile GSTCEFSRC_VERSION is intentionally NOT bumped in this commit — it must stay at 144.0.12 until the workflow has produced and released the 126.2.18 artifact. Follow-up commit after the release upload.

Description

Brief description of the changes.

Related Issue

Fixes #(issue number)

Type of Change

  • Bug fix
  • New feature
  • Breaking change
  • Documentation update

Checklist

  • I have run cargo fmt --all
  • I have run cargo clippy --workspace --all-targets -- -D warnings
  • I have run cargo test --workspace
  • I have updated documentation as needed
  • I have added tests for new functionality

…oryInfra SIGILL

CEF 127+ switched to Chrome runtime by default, introducing a MemoryInfra /
PartitionAlloc CHECK() failure (SIGILL, exit 132) that crashes long-running
cefsrc processes intermittently. No upstream fix exists. CEF 128 removed the
Alloy bootstrap entirely.

Pin the build to:
- CEF 126.2.18+g3647d39+chromium-126.0.6478.183 (last stable Alloy-default)
- gstcefsrc 0e470f51fd (last master commit defaulting to CEF 122, compatible
  with the CEF 126 ABI)

Changes:
- docker/gstcefsrc/Dockerfile: bump default CEF_VERSION, add GSTCEFSRC_REF
  arg, switch clone from --depth 1 to init/fetch/checkout to support
  arbitrary SHAs.
- .github/workflows/build-gstcefsrc.yml: update defaults, add gstcefsrc_ref
  workflow_dispatch input, wire through as --build-arg.
- docker/strom-full/entrypoint.sh: update comment — Chrome-runtime-specific
  flags are no-ops on Alloy but kept as defense-in-depth.
- docs/CEF_SIGILL_CRASH.md: new "Downgrade to CEF 126" section documenting
  rationale and pinning locations; old flag-based fix retained as legacy.

Note: docker/strom-full/Dockerfile GSTCEFSRC_VERSION is intentionally NOT
bumped in this commit — it must stay at 144.0.12 until the workflow has
produced and released the 126.2.18 artifact. Follow-up commit after the
release upload.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
@srperens srperens merged commit 4b4cd66 into main Apr 17, 2026
3 checks passed
@srperens srperens deleted the fix/cef-126-alloy-runtime branch April 17, 2026 10:44
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.

1 participant