mirror of
https://github.com/ArchiveBox/ArchiveBox.git
synced 2026-04-25 17:16:00 +03:00
[GH-ISSUE #1605] Bug: large number of chromium-browser processes spawned by the application causes high memory consumption #3974
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#3974
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 @comatory on GitHub (Nov 28, 2024).
Original GitHub issue: https://github.com/ArchiveBox/ArchiveBox/issues/1605
Originally assigned to: @pirate on GitHub.
Provide a screenshot and describe the bug
I'm having problems on my server caused by lot of
chromium-browserprocesses. It basically makes my server to run out of memory and swap a lot, seehtopoutput:I have many and many processes run by
chromium-browserand I'm not sure why. I was trying to import Pinboard archive (see here) and maybe it somehow caused to stall some jobs or something.All of these processes look like this (there are tens, maybe hundreds of them):
Tearing down the application with
compose downdoes not help.Steps to reproduce
Logs or errors
ArchiveBox Version
How did you install the version of ArchiveBox you are using?
Docker (or other container system like podman/LXC/Kubernetes or TrueNAS/Cloudron/YunoHost/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/CIFS/etc.)data/is on a FUSE mount (e.g. SSHFS/RClone/S3/B2/OneDrive, etc.)Docker Compose Configuration
ArchiveBox Configuration
@pirate commented on GitHub (Nov 28, 2024):
Duplicate of: https://github.com/ArchiveBox/ArchiveBox/issues/746
(It's an old well known issue with a fix in progress)
@comatory commented on GitHub (Nov 28, 2024):
Cool 👍 I'll be waiting for new release then. Strange, I'd expect restarting the containers would help but it doesn't.