starred/karakeep

Fork 0

mirror of https://github.com/karakeep-app/karakeep.git synced 2026-04-24 23:46:06 +03:00

[GH-ISSUE #1978] Browser memory just grows. #1232

New issue

Open

opened 2026-03-02 11:55:57 +03:00 by kerem · 4 comments

kerem commented

2026-03-02 11:55:57 +03:00

Owner

Originally created by @grimwiz on GitHub (Sep 24, 2025).
Original GitHub issue: https://github.com/karakeep-app/karakeep/issues/1978

Describe the Bug

the karakeep web page consumes too much memory, This morning my karakeep tab in Edge had grown to about 6gb and the renderer process was another 6gb which then caused problems (my browser and teams crashed). I've got about 13000 bookmarks and 7500 tags so I've noticed a few challenges. However, As it affected my work I've asked assistance about this bug and the suggestion from ChatGPT's codex was:
Findings

The dashboard renders every fetched bookmark at once: BookmarksGrid spreads the entire bookmarks array into a single element (and the alternate layouts) so none of the earlier cards are ever unmounted as you scroll. Each card also spins up its own React Query subscription in BookmarkCard, so thousands of bookmarks keep their query cache entries, images, and DOM nodes alive simultaneously. With 13 000 bookmarks this produces millions of DOM nodes/decoded images and many live query caches, which quickly pushes Chrome to multi‑gigabyte usage and eventual crashes. The grid needs windowing/virtualization so that only the rows near the viewport mount at any time.

Steps to Reproduce

Open karakeep in Chrome under windows 11 and scroll down. or... have some RSS feeds adding bookmarks and just sit and wait for a few days. I've tested it just now by scrolling down my main page by 20 days of data and hovering over the top tab indicates 1.2Gb of memory is used. My issue earlier was with Edge which may have a different memory management technique but my chrome test just now suggests it's a generic issue.

Expected Behaviour

browser tab memory should not grow beyond a reasonable limit.

Screenshots or Additional Context

Possibly related to this... if you've scrolled down the main page by a reasonable distance you can't move to another tab and come back, something happens to the page where the URL just seems to refresh over and over again without showing the page. tab memory drops to 1Gb and I'm wondering if the browser doesn't preserve enormous tabs properly when they're not focussed?

Device Details

Edge and Chrome on Windows 11.

Exact Karakeep Version

v0.27.1

Have you checked the troubleshooting guide?

I have checked the troubleshooting guide and I haven't found a solution to my problem

Originally created by @grimwiz on GitHub (Sep 24, 2025). Original GitHub issue: https://github.com/karakeep-app/karakeep/issues/1978 ### Describe the Bug the karakeep web page consumes too much memory, This morning my karakeep tab in Edge had grown to about 6gb and the renderer process was another 6gb which then caused problems (my browser and teams crashed). I've got about 13000 bookmarks and 7500 tags so I've noticed a few challenges. However, As it affected my work I've asked assistance about this bug and the suggestion from ChatGPT's codex was: Findings > The dashboard renders every fetched bookmark at once: BookmarksGrid spreads the entire bookmarks array into a single <Masonry> element (and the alternate layouts) so none of the earlier cards are ever unmounted as you scroll. Each card also spins up its own React Query subscription in BookmarkCard, so thousands of bookmarks keep their query cache entries, images, and DOM nodes alive simultaneously. With 13 000 bookmarks this produces millions of DOM nodes/decoded images and many live query caches, which quickly pushes Chrome to multi‑gigabyte usage and eventual crashes. The grid needs windowing/virtualization so that only the rows near the viewport mount at any time. ### Steps to Reproduce Open karakeep in Chrome under windows 11 and scroll down. or... have some RSS feeds adding bookmarks and just sit and wait for a few days. I've tested it just now by scrolling down my main page by 20 days of data and hovering over the top tab indicates 1.2Gb of memory is used. My issue earlier was with Edge which may have a different memory management technique but my chrome test just now suggests it's a generic issue. ### Expected Behaviour browser tab memory should not grow beyond a reasonable limit. ### Screenshots or Additional Context Possibly related to this... if you've scrolled down the main page by a reasonable distance you can't move to another tab and come back, something happens to the page where the URL just seems to refresh over and over again without showing the page. tab memory drops to 1Gb and I'm wondering if the browser doesn't preserve enormous tabs properly when they're not focussed? ### Device Details Edge and Chrome on Windows 11. ### Exact Karakeep Version v0.27.1 ### Have you checked the troubleshooting guide? - [x] I have checked the troubleshooting guide and I haven't found a solution to my problem

kerem added the

bug

status/untriaged

labels

2026-03-02 11:55:57 +03:00

kerem commented

2026-03-02 11:55:58 +03:00

Author

Owner

@grimwiz commented on GitHub (Sep 26, 2025):

Here's a screenshop from today's edge browser, it seems to be triggered particularly by bookmark deletion. The 8gb used at this moment dropped down to 4gb afer a few minutes when the bookmark action completed.

@grimwiz commented on GitHub (Sep 26, 2025): Here's a screenshop from today's edge browser, it seems to be triggered particularly by bookmark deletion. The 8gb used at this moment dropped down to 4gb afer a few minutes when the bookmark action completed. <img width="754" height="343" alt="Image" src="https://github.com/user-attachments/assets/820dda38-6493-416b-801a-93845b51cfe2" />

kerem commented

2026-03-02 11:55:58 +03:00

Author

Owner

@gusvd commented on GitHub (Nov 16, 2025):

Running into a similar issue. I'm running Karakeep on a (small) VPS. I just installed via Docker, and the service - Chromium, more specifically - is consuming all my memory and CPU. To the point, the server is unresponsive and needs to be shut down.

Multiple Chrome instances consuming 3-3.4GB of RAM each
Python3 processes (likely the orchestrator) also getting killed
systemd-journald service failing (system is critically low on memory)
OOM (Out of Memory) killer terminating processes

@gusvd commented on GitHub (Nov 16, 2025): Running into a similar issue. I'm running Karakeep on a (small) VPS. I just installed via Docker, and the service - Chromium, more specifically - is consuming all my memory and CPU. To the point, the server is unresponsive and needs to be shut down. - Multiple Chrome instances consuming 3-3.4GB of RAM each - Python3 processes (likely the orchestrator) also getting killed - systemd-journald service failing (system is critically low on memory) - OOM (Out of Memory) killer terminating processes <img width="2048" height="1222" alt="Image" src="https://github.com/user-attachments/assets/0091016b-3890-4a39-a02f-96068dd1fc35" />

kerem commented

2026-03-02 11:55:58 +03:00

Author

Owner

@MohamedBassem commented on GitHub (Nov 16, 2025):

@gusvd The issue that you're facing is tracked in https://github.com/karakeep-app/karakeep/issues/1748 and I actually recently shared how to control the memory growth of the worker. This issue is about client side memory usage instead.

@MohamedBassem commented on GitHub (Nov 16, 2025): @gusvd The issue that you're facing is tracked in https://github.com/karakeep-app/karakeep/issues/1748 and I actually recently shared how to control the memory growth of the worker. This issue is about client side memory usage instead.

kerem commented

2026-03-02 11:55:58 +03:00

Author

Owner

@gusvd commented on GitHub (Nov 16, 2025):

@gusvd The issue that you're facing is tracked in #1748 and I actually recently shared how to control the memory growth of the worker. This issue is about client side memory usage instead.

So sorry! Feel free to delete it from here. I'll make sure to post in the correct issue with more context.

@gusvd commented on GitHub (Nov 16, 2025): > [@gusvd](https://github.com/gusvd) The issue that you're facing is tracked in [#1748](https://github.com/karakeep-app/karakeep/issues/1748) and I actually recently shared how to control the memory growth of the worker. This issue is about client side memory usage instead. So sorry! Feel free to delete it from here. I'll make sure to post in the correct issue with more context.

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#1232

No description provided.

Rows
Columns