Evidence · DiggingBeagle record
Hermes Agent issue 147739: stale Chromium lock after container recreate
The reporter observed browser-launch failure on seven of ten agents after a container replacement, although the previous process namespace no longer contained a working Chromium.
- Source role
- primary disclosure
Evidence record
The reporter observed browser-launch failure on seven of ten agents after a container replacement, although the previous process namespace no longer contained a working Chromium.
Claim-level citations (1)
- supportsHermes browser sessions can mistake stale Chromium profile locks for living owners: The reporter observed browser-launch failure on seven of ten agents after a container replacement, although the previous process namespace no longer contained a working Chromium.
Issue 147739, shared profile SingletonLock and post-recreate liveness reproduction