mirror of https://github.com/openclaw/openclaw.git
5a2200b280
* fix: detect PID recycling in session write lock staleness check The session lock uses isPidAlive() to determine if a lock holder is still running. In containers, PID recycling can cause a different process to inherit the same PID, making the lock appear valid when the original holder is dead. Record the process start time (field 22 of /proc/pid/stat) in the lock file and compare it during staleness checks. If the PID is alive but its start time differs from the recorded value, the lock is treated as stale and reclaimed immediately. Backward compatible: lock files without starttime are handled with the existing PID-alive + age-based logic. Non-Linux platforms skip the starttime check entirely (getProcessStartTime returns null). * shared: harden pid starttime parsing * sessions: validate lock pid/starttime payloads * changelog: note recycled PID lock recovery fix * changelog: credit hiroki and vincent on lock recovery fix --------- Co-authored-by: HirokiKobayashi-R <hiroki@rhems-japan.co.jp> |
||
|---|---|---|
| .. | ||
| net | ||
| text | ||
| avatar-policy.test.ts | ||
| avatar-policy.ts | ||
| chat-content.ts | ||
| chat-envelope.ts | ||
| config-eval.test.ts | ||
| config-eval.ts | ||
| device-auth.ts | ||
| entry-metadata.ts | ||
| entry-status.ts | ||
| frontmatter.ts | ||
| gateway-bind-url.ts | ||
| model-param-b.ts | ||
| node-list-parse.test.ts | ||
| node-list-parse.ts | ||
| node-list-types.ts | ||
| node-match.ts | ||
| operator-scope-compat.test.ts | ||
| operator-scope-compat.ts | ||
| pid-alive.test.ts | ||
| pid-alive.ts | ||
| process-scoped-map.ts | ||
| requirements.test.ts | ||
| requirements.ts | ||
| shared-misc.test.ts | ||
| string-normalization.test.ts | ||
| string-normalization.ts | ||
| subagents-format.ts | ||
| tailscale-status.ts | ||
| text-chunking.ts | ||
| usage-aggregates.ts | ||