Nick Sweeting

`docker-compoes run archivebox config --set TIMEOUT=240` or just change your TIMEOUT line in docker-compose.yml: ```yaml ... environment: - TIMEOUT=240 ```

If there's no change then it's probably not a timeout issue, the images are probably just not archivable with those methods for that particular site.

Can you post the docker logs from the archiving / the output of running the wget command that archivebox runs (you can find it in the logs).

ArchiveBox Singlefile is gildas-lormeau/SingleFile.

Could be because we aren't using the latest version, SingleFile is adding new features all the time and we're a bit behind. The next ArchiveBox release will bump it to...

Please post the full output of `archivebox --version`. I suspect it's the Chrome orphan child problem we've been before https://github.com/ArchiveBox/ArchiveBox/issues/550 (Chrome is naughty by forking some child processes that it...

Hmm it's the latest version which should have the fix. Can you check if the high resource use is by chromium or a different process using `htop`? (sort by CPU...

Yeah ok, this is an annoying known bug we've seen a few times with Chromium. Can you try the fix I just put on `dev` by building a new docker...

Can you screenshot htop again, but scroll over to the right a bit more to see the full chrome args? I think that'll tell us what extractor is running chrome....

Looks like you have `--single-process --no-zygote` in the args anyway, so my idea was wrong. That chrome proc shouldn't leave behind any orphan processes with `--single-process --no-zygote` (in theory).