Bug 134306 - The undo information for inserting a row in a large sheet is +/- 200 MB. Tracking changes needs only 45 MB
Summary: The undo information for inserting a row in a large sheet is +/- 200 MB. Trac...
Status: RESOLVED INSUFFICIENTDATA
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Calc (show other bugs)
Version:
(earliest affected)
4.4.7.2 release
Hardware: All All
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2020-06-25 17:46 UTC by Telesto
Modified: 2022-11-30 03:49 UTC (History)
2 users (show)

See Also:
Crash report or crash signature:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Telesto 2020-06-25 17:46:47 UTC
Description:
The undo information for inserting a row in a large sheet is 200 MB. Tracking changes needs 45 MB. So I assume some room for improvement

Steps to Reproduce:
1. Open attachment 161647 [details]
2. Copy column A-C
3. Paste it always next the other, so DEF GHI KLM NOP 
4. Open an process manager
5. Insert a row -> Notice a bump of 200 MB
6. Go to tools -> options -> LibreOfficeDev -> Advanced. Open expert Configuration & search for Undo (Steps) reduce it from 100 to 0
7. Quite LibreOffice
8. Open the attached file again
9. Repeat step 2/3
10. Edit -> Track and changes -> Record
11. Have the process manager still around
12. Insert a row -> Take notice of the memory bump (50 MB)
13. Edit -> Track and changes -> Manage
14. Reject change.. 
	
Related in some way bug 134301

Actual Results:
Undo needs by far more ram for the same 'undo' information

Expected Results:
Something similar to tracking changes would be nice..


Reproducible: Always


User Profile Reset: No



Additional Info:
Version: 7.1.0.0.alpha0+ (x64)
Build ID: 006c65bbd472cb1d7d44e095714e28190b76be0d
CPU threads: 4; OS: Windows 6.3 Build 9600; UI render: default; VCL: win
Locale: nl-NL (nl_NL); UI: en-US
Calc: CL
Comment 1 Buovjaga 2021-07-25 10:36:46 UTC
(In reply to Telesto from comment #0)
> Description:
> The undo information for inserting a row in a large sheet is 200 MB.
> Tracking changes needs 45 MB. So I assume some room for improvement
> 
> Steps to Reproduce:
> 1. Open attachment 161647 [details]
> 2. Copy column A-C
> 3. Paste it always next the other, so DEF GHI KLM NOP 
> 4. Open an process manager
> 5. Insert a row -> Notice a bump of 200 MB

The bump for me is only 1MB. You didn't mention where to insert it, so I inserted it between rows 1 and 2. Can you re-test?

NixOS
Version: 7.3.0.0.alpha0+ / LibreOffice Community
Build ID: 67e47070a7580a17804adce812cc2f98bfe7b51f
CPU threads: 16; OS: Linux 5.13; UI render: default; VCL: x11
Locale: fi-FI (fi_FI.UTF-8); UI: en-US
Calc: threaded
Comment 2 Xisco Faulí 2022-05-02 12:03:52 UTC
Dear Telesto,
Could you please try to reproduce it with a master build from http://dev-builds.libreoffice.org/daily/master/ ?
You can install it alongside the standard version.
I have set the bug's status to 'NEEDINFO'. Please change it back to 'UNCONFIRMED' if the bug is still present in the master build
Comment 3 QA Administrators 2022-10-30 03:48:04 UTC Comment hidden (obsolete)
Comment 4 QA Administrators 2022-11-30 03:49:44 UTC
Dear Telesto,

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

MassPing-NeedInfo-FollowUp