Bug 59365 - FILESAVE: Memory usage after autorecovery/manual savings
Summary: FILESAVE: Memory usage after autorecovery/manual savings
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Writer (show other bugs)
(earliest affected)
3.5.4 release
Hardware: All All
: medium normal
Assignee: Not Assigned
Whiteboard: BSA
Depends on:
Blocks: AutoSave-AutoRecovery-Backup Memory
  Show dependency treegraph
Reported: 2013-01-14 15:32 UTC by karolismatjosaitis
Modified: 2024-02-12 03:12 UTC (History)
1 user (show)

See Also:
Crash report or crash signature:


Note You need to log in before you can comment on or make changes to this bug.
Description karolismatjosaitis 2013-01-14 15:32:44 UTC
Problem description: 
First of all, I reduced libreoffice memory settings to minimum, because it used ~ 1 Gb of RAM, but it didn't worked. A problem persists. Operative memory usage increases gradually when:
1) opening two writer documents in odt format: one was ~ 20 Mb in size.
2) Memory usage increased while working with writer after every autorecovery (it was set up to 30 min) saving, or (when autorecovery is turn off) after saving manually.
3) memory usage doesn't decrease after savings are completed.
Steps to reproduce:
1.for better effect, increase memory settings (for example in Graphic cache: 50 Mb for office, 8 mb per object, quickstarter enabled)
2. Try to save bigger (>20 mb) document, after editing, few times (manually or by autorecovery).

Current behavior:

Expected behavior:
I spouse operative memory should decrease after saving document, but not increase gradually after every saving.
Operating System: Ubuntu
Version: 3.5.4 release
Comment 1 Joel Madero 2013-06-24 01:49:09 UTC
Unfortunately this and similar RAM issues have been known and are legacy from OOo. 

This being said the issue has been reported multiple times and developers are well aware of it. Fixing it will take weeks of developers time (thousands of dollars if done professionally and very complicated for volunteers)

I am marking this as NEW but note that we do in fact know about the issue and maybe at some point someone will have the time (or get paid) to fix it. 

In reality I am positive this is a duplicate of other RAM issues - if someone stumbled across a bug ID that talks about RAM not being freed up please mark this as a duplicate.

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
LibreOffice is powered by a team of volunteers, every bug is confirmed (triaged) by human beings who mostly give their time for free. We invite you to join our triaging by checking out this link:
https://wiki.documentfoundation.org/QA/BugTriage and join us on freenode at #libreoffice-qa

There are also other ways to get involved including with marketing, UX, documentation, and of course developing -  http://www.libreoffice.org/get-help/mailing-lists/. 

Lastly, good bug reports help tremendously in making the process go smoother, please always provide reproducible steps (even if it seems easy) and attach any and all relevant material
Comment 2 QA Administrators 2015-06-08 14:41:36 UTC Comment hidden (obsolete)
Comment 3 QA Administrators 2016-09-20 10:00:31 UTC Comment hidden (obsolete)
Comment 4 QA Administrators 2021-01-11 03:56:43 UTC Comment hidden (obsolete, spam)
Comment 5 QA Administrators 2023-01-12 03:21:06 UTC Comment hidden (obsolete, spam)
Comment 6 Justin L 2023-07-15 23:20:33 UTC
This has been untouched for 10 years. It really needs to be confirmed that current LibreOffice still consumes memory during each save. That will be especially important to know for LO 7.6 because it turns on autosave/backups.
Comment 7 QA Administrators 2024-01-12 03:13:13 UTC Comment hidden (obsolete)
Comment 8 QA Administrators 2024-02-12 03:12:29 UTC
Dear karolismatjosaitis,

Please read this message in its entirety before proceeding.

Your bug report is being closed as INSUFFICIENTDATA due to inactivity and
a lack of information which is needed in order to accurately
reproduce and confirm the problem. We encourage you to retest
your bug against the latest release. If the issue is still
present in the latest stable release, we need the following
information (please ignore any that you've already provided):

a) Provide details of your system including your operating
   system and the latest version of LibreOffice that you have
   confirmed the bug to be present

b) Provide easy to reproduce steps – the simpler the better

c) Provide any test case(s) which will help us confirm the problem

d) Provide screenshots of the problem if you think it might help

e) Read all comments and provide any requested information

Once all of this is done, please set the bug back to UNCONFIRMED
and we will attempt to reproduce the issue. Please do not:

a) respond via email 

b) update the version field in the bug or any of the other details
   on the top section of our bug tracker

Warm Regards,
QA Team