[GH-ISSUE #3714] [FR] Free RAM #1681

New issue

Open

opened 2026-03-23 21:15:57 +00:00 by mirror · 2 comments

mirror commented

2026-03-23 21:15:57 +00:00

Owner

Originally created by @Rasterisko on GitHub (Oct 16, 2023).
Original GitHub issue: https://github.com/AppFlowy-IO/AppFlowy/issues/3714

Originally assigned to: @LucasXu0 on GitHub.

Description

As the notes are opened, they accumulate in the RAM memory. It would be really nice if the app freed up the RAM when a note was closed.

Impact

There would be no risk of using too much RAM even with a lot of notes and images.

Additional Context

Using AppImage in Linux Mint 21.1 XFCE.

To add more information I did a simple test. I openned a new folder and inserted a new note just with a calendar:

Them, I started to change between the two notes. The ram has started to go up indicating that for every time a note is opened, it is loaded into the ram memory, even if it has already been opened previously:

After about 1 minute of doing this, I got to +100MB of RAM accumulated as the screenshot shows. I waited about 20min to see if the RAM would decrease, but the consumption remains the same. This may seem like an exaggerated test at first, but I believe it is not. A user with a lot of notes that contain calendars, images, tables, etc. will probably reach a very high RAM consumption after some short time of use if they are constantly browsing between their notes.

I think I can't say this is a bug, so that's why I openned like a Feature Request.

Originally created by @Rasterisko on GitHub (Oct 16, 2023). Original GitHub issue: https://github.com/AppFlowy-IO/AppFlowy/issues/3714 Originally assigned to: @LucasXu0 on GitHub. ### Description As the notes are opened, they accumulate in the RAM memory. It would be really nice if the app freed up the RAM when a note was closed. ### Impact There would be no risk of using too much RAM even with a lot of notes and images. ### Additional Context Using AppImage in Linux Mint 21.1 XFCE. To add more information I did a simple test. I openned a new folder and inserted a new note just with a calendar: ![Início do programa consumo RAM](https://github.com/AppFlowy-IO/AppFlowy/assets/95868625/1852c35b-b9f2-4df2-bbd3-ad394f622cb8) Them, I started to change between the two notes. The ram has started to go up indicating that for every time a note is opened, it is loaded into the ram memory, even if it has already been opened previously: ![Depois de algumas trocas consumo RAM](https://github.com/AppFlowy-IO/AppFlowy/assets/95868625/20b53a5a-0cc3-430e-b1f3-e3a2dcfab1f2) After about 1 minute of doing this, I got to +100MB of RAM accumulated as the screenshot shows. I waited about 20min to see if the RAM would decrease, but the consumption remains the same. This may seem like an exaggerated test at first, but I believe it is not. A user with a lot of notes that contain calendars, images, tables, etc. will probably reach a very high RAM consumption after some short time of use if they are constantly browsing between their notes. I think I can't say this is a bug, so that's why I openned like a Feature Request.

mirror added the

2024

bug

labels

2026-03-23 21:15:57 +00:00

mirror commented

2026-03-23 21:15:58 +00:00

Author

Owner

@Xazin commented on GitHub (Mar 2, 2024):

I can't see that the RAM accumulates, I'm on MacOS and it seems like it falls accurately depending on current open document/database.

We did do some disposal of resources not long ago, and we definitely do not store all opened documents in RAM for the whole app lifecycle, that would have been really bad and also way more noticeable.

Can you double check that this is no longer an issue and close if needed @LucasXu0 ?

@Xazin commented on GitHub (Mar 2, 2024): I can't see that the RAM accumulates, I'm on MacOS and it seems like it falls accurately depending on current open document/database. We did do some disposal of resources not long ago, and we definitely do not store all opened documents in RAM for the whole app lifecycle, that would have been really bad and also way more noticeable. Can you double check that this is no longer an issue and close if needed @LucasXu0 ?

mirror commented

2026-03-23 21:15:58 +00:00

Author

Owner

@Rasterisko commented on GitHub (Jun 23, 2024):

Hello again,

I tested here using the last version 0.6.1 and it seems to accumulate faster now.

@Rasterisko commented on GitHub (Jun 23, 2024): Hello again, I tested here using the last version 0.6.1 and it seems to accumulate faster now. ![aa](https://github.com/AppFlowy-IO/AppFlowy/assets/95868625/51cefb5e-e6d6-46ae-985d-b57a4bda4c6c)