fix(docker): replace non-existent CEF tracing flag with working alternatives#461
Merged
fix(docker): replace non-existent CEF tracing flag with working alternatives#461
Conversation
…king flags The Chromium switch "disable-background-tracing" does not exist (verified in Chromium 144 source and libcef.so binary). Only "enable-background-tracing" exists as an opt-in flag. The previous flag was silently ignored, leaving the MemoryInfra periodic dump system active and causing intermittent SIGILL crashes (exit code 132) in long-running CEF processes. Replace with flags that actually prevent MemoryInfra from running: - disable-features=BackgroundTracing (disables the feature entirely) - no-periodic-tasks (prevents periodic dump scheduling) - force-fieldtrials= (clears field trial configs that enable tracing) Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
disable-background-tracingdoes not exist — verified in both Chromium 144 source (tracing_switches.cc) and by binary string search oflibcef.so. Onlyenable-background-tracingexists (opt-in). The flag was silently ignored.libcef.soand target the correct mechanisms:disable-features=BackgroundTracing,no-periodic-tasks,force-fieldtrials=Test plan
core.MemoryInfra.*core dumps appear🤖 Generated with Claude Code