mirror of
https://github.com/ArchiveBox/ArchiveBox.git
synced 2026-04-25 17:16:00 +03:00
[GH-ISSUE #1651] Bug: Archivebox will expand to crash host machine when a lot of crawls are scheduled #4004
Labels
No labels
expected: maybe someday
expected: next release
expected: release after next
expected: unlikely unless contributed
good first ticket
help wanted
pull-request
scope: all users
scope: windows users
size: easy
size: hard
size: medium
size: medium
status: backlog
status: blocked
status: done
status: idea-phase
status: needs followup
status: wip
status: wontfix
touches: API/CLI/Spec
touches: configuration
touches: data/schema/architecture
touches: dependencies/packaging
touches: docs
touches: js
touches: views/replayers/html/css
why: correctness
why: functionality
why: performance
why: security
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/ArchiveBox#4004
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @AramZS on GitHub (Feb 4, 2025).
Original GitHub issue: https://github.com/ArchiveBox/ArchiveBox/issues/1651
Originally assigned to: @pirate on GitHub.
Provide a screenshot and describe the bug
I may be running archivebox on a machine a little below what is expected (an RPi 3) but I am regularly hitting it maxing out to all available RAM until it crashes the host machine. This seems undesirable. It is not in the documentation that I can see, but I would think that a good solution might be allowing the configuration in Docker Compose for anyone running the self-hosted browser-facing version of the application to set a limit on the number of Chrome instances the system can launch and keep up simultaneously to not hit the limit. 10 gigs of memory is not huge, but it isn't nothing either and I think being able to avoid dropping a machine with that amount of memory available is a desirable feature.
I'd be glad to try my hand at this if you can point me in the right direction, I'm just getting familiar with the code base here now, but I would like to contribute if it seems this is a good place to start. Also, I'm just starting, so maybe I just screwed up the config somewhere.
Steps to reproduce
Logs or errors
ArchiveBox Version
How did you install the version of ArchiveBox you are using?
Docker (or Podman/LXC/K8s/TrueNAS/Proxmox/etc)
What operating system are you running on?
Linux (Ubuntu/Debian/Arch/Alpine/etc.)
What type of drive are you using to store your ArchiveBox data?
data/is on a local SSD or NVMe drivedata/is on a spinning hard drive or external USB drivedata/is on a network mount (e.g. NFS/SMB/Ceph/GlusterFS/etc.)data/is on a FUSE mount (e.g. SSHFS/RClone/S3/B2/Google Drive/Dropbox/etc.)Docker Compose Configuration
ArchiveBox Configuration
@pirate commented on GitHub (Feb 5, 2025):
Thanks for reporting, it's actually this well known issue, please subscribe over there for updates: https://github.com/ArchiveBox/ArchiveBox/issues/746