[GH-ISSUE #2369] [bug] Chromium containers stuck with high idle CPU after large imports #1432

Open
opened 2026-03-02 11:57:19 +03:00 by kerem · 2 comments
Owner

Originally created by @Emstar on GitHub (Jan 10, 2026).
Original GitHub issue: https://github.com/karakeep-app/karakeep/issues/2369

First, thanks for sharing this project and especially thanks for making the setup instructions complete. Too many times have little details like the .env file been left out project documentation! I was easily able to spin up Karakeep 0.30.0 on Ubuntu and feed it my list of HTML bookmarks from Firefox. It took about 9 hours but it chewed through about 2900 links, though I didn't set up AI stuff yet. Cool.

However, while Karakeep tells me it is done, and Background Jobs shows nothing is queued up, I have about a dozen chromium processes active, consuming a lot of CPU. These processes have been running for hours. I assume this is not intended behavior.

I restarted the container, and a handful of chromium processes returned, but they were all idle. That seemed pretty reasonable.

If I get a stuck chromium process again... What should I do, besides restarting to clean it up? Is there anything I should look at to find info for a formal bug report?

Originally created by @Emstar on GitHub (Jan 10, 2026). Original GitHub issue: https://github.com/karakeep-app/karakeep/issues/2369 First, thanks for sharing this project and especially thanks for making the setup instructions complete. Too many times have little details like the .env file been left out project documentation! I was easily able to spin up Karakeep 0.30.0 on Ubuntu and feed it my list of HTML bookmarks from Firefox. It took about 9 hours but it chewed through about 2900 links, though I didn't set up AI stuff yet. Cool. However, while Karakeep tells me it is done, and Background Jobs shows nothing is queued up, I have about a dozen chromium processes active, consuming a _lot_ of CPU. These processes have been running for _hours_. I assume this is not intended behavior. I restarted the container, and a handful of chromium processes returned, but they were all idle. That seemed pretty reasonable. If I get a stuck chromium process again... What should I do, besides restarting to clean it up? Is there anything I should look at to find info for a formal bug report?
Author
Owner

@MohamedBassem commented on GitHub (Jan 10, 2026):

@Emstar this is a behavior I've recently started observing as well, I think it's a bug somewhere. Will make it as such so that we can try to debug it.

<!-- gh-comment-id:3732496056 --> @MohamedBassem commented on GitHub (Jan 10, 2026): @Emstar this is a behavior I've recently started observing as well, I think it's a bug somewhere. Will make it as such so that we can try to debug it.
Author
Owner

@MohamedBassem commented on GitHub (Feb 22, 2026):

I've sent https://github.com/karakeep-app/karakeep/pull/2503 as a way to mitigate this issue, and will be included in the next release happening today.

<!-- gh-comment-id:3940517906 --> @MohamedBassem commented on GitHub (Feb 22, 2026): I've sent https://github.com/karakeep-app/karakeep/pull/2503 as a way to mitigate this issue, and will be included in the next release happening today.
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
starred/karakeep#1432
No description provided.