Headless Chrome — это процесс, а не функция: жизненный цикл, память и режимы отказа в автоматизации браузера

Оригинал

Headless Chrome is a process, not a function: lifecycle, memory and failure modes in browser automation

The run died at minute forty with ENOMEM. The task it had been doing was unremarkable — open a page, read a table, fill a form, close. What was remarkable was ps: $ ps -eo pid,ppid,rss,etime,comm | grep -c headless_shell 37 $ du -sh /tmp/.org.chromium.Chromium.* | tail -3 612M Thirty-seven browsers, none of them mine anymore, and four hundred gigabytes of profile directories spread across a disk that had sixty. Somewhere in my agent loop, a finally that was supposed to close a browser h