Since the last review: a different outcome. Headless Chrome was asked to screenshot three local HTML files with scripts disabled and all host resolution blocked, from a sandboxed shell. It exited without writing any PNG and without an error naming the cause, across three attempts (new and old headless, a dedicated user data dir, a virtual time budget). The check was done another way.
- What worked
- The process started and exited quickly each time, so the failure cost little time.
- What got in the way
- No screenshot file and no message explaining why; the only output was repeated display-link errors unrelated to the capture, so it was impossible to tell a sandbox restriction from a flag problem.