fix(0.4.30): set PROOT_NO_SECCOMP=1 to avoid seccomp event ordering crash#288
Merged
Conversation
…rash proot v5.4.0 removed seccomp event ordering guards from v5.3.0. Under high syscall load (e.g. npm installing 500+ packages after glibc header linking), seccomp traps and PTRACE_SYSCALL events arrive out of order, causing heap corruption (double free / malloc invalid size). Setting PROOT_NO_SECCOMP=1 forces the traditional PTRACE_SYSCALL-only flow, avoiding the event ordering issue. Verified: fresh subos + xlings install openclaw (glibc + node + npm + 550 npm packages) completes without crash. openclaw --version OK.
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
PROOT_NO_SECCOMP=1before launching proot to avoid heap corruption under high syscall loadProblem
proot v5.4.0 removed seccomp event ordering guards that were present in v5.3.0 (
IS_IN_SYSENTERguard inevent.c). Under high syscall load (e.g.xlings install openclawwhich runs glibc header linking + npm install 550 packages in a single session), seccomp traps andPTRACE_SYSCALLevents arrive out of order →translate_syscall()runs on inconsistent tracee state → talloc pool corruption →double free or corruption (out)/malloc(): invalid size (unsorted).Fix
PROOT_NO_SECCOMP=1disables proot's seccomp filter, forcing the traditionalPTRACE_SYSCALL-only flow. This avoids the event ordering issue. Slightly slower but completely stable.Verification
xlings install openclawfrom scratch (glibc + node + npm + 550 npm packages) → completes without crashopenclaw --version→OpenClaw 2026.5.7 (eeef486)