Bug 133463 - Much more memory usage while saving is much and a part tends do stick around
Summary: Much more memory usage while saving is much and a part tends do stick around
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Writer (show other bugs)
(earliest affected) release
Hardware: All All
: medium minor
Assignee: Not Assigned
Keywords: bibisected, bisected, perf
Depends on:
Blocks: Memory
  Show dependency treegraph
Reported: 2020-05-27 21:18 UTC by Telesto
Modified: 2020-06-18 18:09 UTC (History)
3 users (show)

See Also:
Crash report or crash signature:
Regression By:

Bibisect log (2.97 KB, text/plain)
2020-05-27 21:20 UTC, Telesto

Note You need to log in before you can comment on or make changes to this bug.
Description Telesto 2020-05-27 21:18:57 UTC
Much more memory usage while saving is much and a part tends do stick around

Steps to Reproduce:
1. Open Process Explorer (or any other tool capable of monitoring mem usage)
2. Open LibreOffice (Start Center) & take notice of memory usage
4. Open attachment 160498 [details] 
5. Take notice of the initial memory required
6. Move the Sat Lite Logo a little
5. Press Save -> Take notice of memory development
6. Close the file (back to start center) (take notice of memory usage
7. Reopen the file (take notice of memory usage; compare with initial opening)
8. Save again (take notice of the memory usage; compare with previous save)
9. Close again (take notice of the memory usage and compare with the first close)

Actual Results:
Memory use has a peak while saving.. With 4.2 only 80 MB is used while saving 
This changed with 4.4. Memory increased from 80 to 180 mb peak.. It also growing

Expected Results:
Pff, no clue what the current situation would be.. but ideally not climbing memory.. in Writer.. this started here.. 
The memory usage increasing on each and every save is really noticeable on MacOS

Reproducible: Always

User Profile Reset: No

Additional Info:
Version: (x64)
Build ID: 21875558f6c478f07d68ff39e025d7ffd451674f
CPU threads: 4; OS: Windows 6.3 Build 9600; UI render: Skia/Raster; VCL: win
Locale: nl-NL (nl_NL); UI: en-US
Calc: CL

Comment 1 Telesto 2020-05-27 21:20:14 UTC
Created attachment 161357 [details]
Bibisect log

Bisected to:
author	Zolnai Tamás <tamas.zolnai@collabora.com>	2014-11-07 16:53:47 +0100
committer	Zolnai Tamás <tamas.zolnai@collabora.com>	2014-11-07 16:54:58 +0100
commit 5771bde234ec65d79501d5eab938e06dfe43e232 (patch)
tree e2855ef4f3bc1ddbeaa418ee8107c2e91eab742d
parent 673f3dfc3cc4190a01001280330ff0b63cd1cc7f (diff)
Try to fix ambiguity error

Comment 2 Telesto 2020-05-27 21:27:05 UTC
Another request..
Comment 3 b. 2020-05-28 15:58:46 UTC
see some use in and, but not a big issue ... 

one should look for it, but crashes, wrong calculations, performance (wasting time of users) and some others are more critical, ram is cheap nowadays ...
Comment 4 Telesto 2020-05-28 19:50:25 UTC
Adding CC to Zolnai Tamás
Comment 5 Buovjaga 2020-06-18 18:09:51 UTC
Discussed this in the dev chat as well and let's close