Bug 164812 - LibreOffice Writer v24 consumes 200-500 MB more RAM than v6, is it possible a memory leak?
Summary: LibreOffice Writer v24 consumes 200-500 MB more RAM than v6, is it possible a...
Status: RESOLVED WORKSFORME
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Writer (show other bugs)
Version:
(earliest affected)
24.8.4.2 release
Hardware: x86-64 (AMD64) Windows (All)
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2025-01-23 09:32 UTC by Aertx
Modified: 2025-05-09 10:18 UTC (History)
1 user (show)

See Also:
Crash report or crash signature:


Attachments
LibreOffice v24 RAM using (14.09 KB, image/png)
2025-02-13 03:20 UTC, Aertx
Details
RAM vs6 VS v24 (15.11 KB, image/png)
2025-02-13 03:44 UTC, Aertx
Details
Docs for compare RAM Leak "v24 skia yes VS skia no" (528.91 KB, application/x-zip-compressed)
2025-03-10 12:55 UTC, Aertx
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Aertx 2025-01-23 09:32:44 UTC

    
Comment 1 Aertx 2025-01-23 09:37:20 UTC
1) Ситуация прочявляется когда открыто например 15 документов с высотой страниц 300 метров и по 60 таблиц
Comment 2 Aertx 2025-01-23 09:38:29 UTC
*1) Ситуация проявляется когда открыто например 15 документов с высотой страниц 3 метров и содержащих 60 малых таблиц
Comment 3 Julien Nabet 2025-01-23 10:39:04 UTC
From Google translate
"The situation appears when, for example, 15 documents are opened with a page height of 3 meters and containing 60 small tables"
Comment 4 mikhail.machine 2025-02-04 08:30:57 UTC
Hello Aertx,

Thank you for reporting the bug. Please attach a sample document, as this makes it easier for us to verify the bug. 
(Please note that the attachment will be public; remove any sensitive information before attaching it. 
See <https://wiki.documentfoundation.org/QA/FAQ#sanitize> for help on how to do so.)

Благодарю Вас за сообщение об ошибке. Не могли бы Вы к сообщению добавить дополнительную визуальную информацию, это позволит нам быстрее провести верификацию ошибки.
(Обращаю Ваше внимание на то, что все прикрепленные файлы являются публичными; удалите из них информацию частного характера)
Comment 5 Aertx 2025-02-13 03:20:59 UTC
Created attachment 199179 [details]
LibreOffice v24 RAM using

LibreOffice v24 RAM using
Comment 6 Aertx 2025-02-13 03:44:20 UTC
Created attachment 199180 [details]
RAM vs6 VS v24
Comment 7 Buovjaga 2025-02-13 05:17:34 UTC
(In reply to Aertx from comment #5)
> Created attachment 199179 [details]
> LibreOffice v24 RAM using
> 
> LibreOffice v24 RAM using

These are not example documents, but screenshots. In any case, a memory leak is something where the amount of used memory keeps growing steadily.

You compare the used amount with version 6, so there is a large difference in terms of code changes. Using more memory is not inherently bad. It can just be a different way of handling things, like caching something vs. processing it with CPU over and over again.
Comment 8 Aertx 2025-02-16 15:05:42 UTC
This is Skia, disabling Skia helps to solve this leak, but lags occur.
In v25 this was solved, the leak with Skia disappeared.
Could you solve the same for v24?
Comment 9 Buovjaga 2025-02-16 15:26:30 UTC
(In reply to Aertx from comment #8)
> This is Skia, disabling Skia helps to solve this leak, but lags occur.
> In v25 this was solved, the leak with Skia disappeared.
> Could you solve the same for v24?

Yes, we could solve it for 24.8, if we could see the problem. Without example documents we can't see it.

However, it is possible for you to find out the fixing commit in 25.2:

https://wiki.documentfoundation.org/QA/Bibisect
Especially: https://wiki.documentfoundation.org/QA/Bibisect#Finding_a_fix
https://wiki.documentfoundation.org/QA/Bibisect/Windows
Comment 10 Aertx 2025-03-10 12:55:25 UTC
Created attachment 199720 [details]
Docs for compare RAM Leak "v24 skia yes VS skia no"
Comment 11 Buovjaga 2025-05-09 10:18:59 UTC
Sorry, I did not have time to find the fix and the final version of 24.8 was released yesterday, so let's close.