-
Just checking to see if it is just me, or a network issue or a new version glitch. Try this maybe which is in my list https://arstechnica.com/?p=1995005
|
Beta Was this translation helpful? Give feedback.
Replies: 1 comment 2 replies
-
Looks like Chromium Ugh, this issue pops up every few Chromium releases, it's not the first time it's happened. cypress-io/cypress#27264 It seems to run successfully and then just hang when its supposed to exit. At the moment there's not a ton I can do as it's not something ArchiveBox can control, but I'll keep troubleshooting. You can verify that it's Chrome failing by running a very simple chrome headless command and seeing if it hangs indefinitely: "/Applications/Google Chrome.app/Contents/MacOS/Google Chrome" --headless=new --no-sandbox --no-zygote --disable-dev-shm-usage --disable-sync --dump-dom "https://arstechnica.com/?p=1995005"
# or in docker
docker run -it -v $PWD/data:/data archivebox:test /usr/bin/chromium-browser --headless=new --no-sandbox --no-zygote --disable-dev-shm-usage --disable-sync --dump-dom "https://arstechnica.com/?p=1995005" |
Beta Was this translation helpful? Give feedback.
Looks like Chromium
120.0.6099.28
is randomly hanging before exit (again) which causes Screenshot, DOM, PDF, and Singlefile to fail.Ugh, this issue pops up every few Chromium releases, it's not the first time it's happened. cypress-io/cypress#27264
It seems to run successfully and then just hang when its supposed to exit.
A bunch of the failing methods actually produce correct output, but ArchiveBox logs them as failed because they time out.
At the moment there's not a ton I can do as it's not something ArchiveBox can control, but I'll keep troubleshooting.
For now you can downgrade chrome or wait a few hours and try again, it often just fixes itself.
You can verify that it's Chrome fail…