Download it now!
Bug 125492 - Memory usage is heavily increasing on every table formatting style switch (large table)
Summary: Memory usage is heavily increasing on every table formatting style switch (la...
Status: NEW
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Writer (show other bugs)
Version:
(earliest affected)
4.4.7.2 release
Hardware: All All
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords: perf
Depends on:
Blocks: Writer-Tables-Style
  Show dependency treegraph
 
Reported: 2019-05-25 16:53 UTC by Telesto
Modified: 2019-06-01 15:24 UTC (History)
1 user (show)

See Also:
Crash report or crash signature:


Attachments
Example file (36.36 KB, application/vnd.oasis.opendocument.text)
2019-05-25 16:54 UTC, Telesto
Details
Screencast (3.09 MB, video/mp4)
2019-06-01 11:19 UTC, Telesto
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Telesto 2019-05-25 16:53:52 UTC
Description:
Memory usage is heavily increasing on every table formatting style switch (large table)

Steps to Reproduce:
1. Open the attached file
2. Open a process monitor tool
3. Place the cursor in the first table
4. Table -> Autoformat styles -> Press OK
5. Table -> Autoformat styles -> Select the next style & press OK
6. Repeat 4 (few times)

Actual Results:
Large memory bumps on every change

Expected Results:
A bit more efficient behavior 


Reproducible: Always


User Profile Reset: No



Additional Info:
Version: 6.3.0.0.alpha1+
Build ID: f5b9590fc06811a9dff550c6998d1d1088507e23
CPU threads: 4; OS: Windows 6.3; UI render: default; VCL: win; 
Locale: nl-NL (nl_NL); UI-Language: en-US
Calc: CL
Comment 1 Telesto 2019-05-25 16:54:11 UTC
Created attachment 151675 [details]
Example file
Comment 2 Dieter 2019-06-01 09:49:23 UTC
I can't confirm that with

Version: 6.3.0.0.alpha1+ (x64)
Build ID: e92dcfdc7bd7b237e0bee26ff226a102d9e8e766
CPU threads: 4; OS: Windows 10.0; UI render: default; VCL: win; 
TinderBox: Win-x86_64@42, Branch:master, Time: 2019-05-14_00:00:57
Locale: en-US (de_DE); UI-Language: en-US
Calc: threaded
Comment 3 Telesto 2019-06-01 11:19:59 UTC
Created attachment 151826 [details]
Screencast

Version: 6.3.0.0.alpha1+
Build ID: 63b39fe87644587210214198fb67d6b3fb3343c5
CPU threads: 4; OS: Windows 6.3; UI render: default; VCL: win; 
TinderBox: Win-x86@42, Branch:master, Time: 2019-05-27_01:42:59
Locale: it-IT (nl_NL); UI-Language: en-US
Calc: CL
Comment 4 Dieter 2019-06-01 11:41:05 UTC
I'm sorry Telesto, but I mixed up CPU and memory usage.

I confirm the bug with

Version: 6.3.0.0.alpha1+ (x64)
Build ID: e92dcfdc7bd7b237e0bee26ff226a102d9e8e766
CPU threads: 4; OS: Windows 10.0; UI render: default; VCL: win; 
TinderBox: Win-x86_64@42, Branch:master, Time: 2019-05-14_00:00:57
Locale: en-US (de_DE); UI-Language: en-US
Calc: threaded
Comment 5 Telesto 2019-06-01 11:49:20 UTC
(In reply to Dieter Praas from comment #4)
> I'm sorry Telesto, but I mixed up CPU and memory usage.
> 
No problem, can happen. I'm already happy someone is (un)confirming my reports :-). I'm probably a bit of a pain in the ass QA/Developers with all my bug reports
Comment 6 Dieter 2019-06-01 15:24:22 UTC
(In reply to Telesto from comment #5)
> I'm already happy someone is (un)confirming my
> reports :-). I'm probably a bit of a pain in the ass QA/Developers with all
> my bug reports

Could be :-) Sometime I wish we could reduce reporting bugs until we have less than 200 unconfirmed bugs.