[Libreoffice-bugs] [Bug 125687] Extreme memory usage opening/saving a large ODS with tracking changed enabled

bugzilla-daemon at bugs.documentfoundation.org bugzilla-daemon at bugs.documentfoundation.org
Thu Oct 24 07:10:53 UTC 2019


https://bugs.documentfoundation.org/show_bug.cgi?id=125687

b. <newbie-02 at gmx.de> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|RESOLVED                    |NEW
         Resolution|DUPLICATE                   |---
     Ever confirmed|0                           |1

--- Comment #3 from b. <newbie-02 at gmx.de> ---

@Telesto: nice stresstest, nice apt comment, thumb up, 

@all: to pinpoint a bug it's good practice to reduce size, impact and
complexity to a minimum, to prove overall correctness it's neccessary to boost
size, impact and complexity to a maximum, 

@Xisco: imho you're wrong, this bug is not about 'comments' (red dot in upper
right corner of cell), but about 'change notes' (red dot in upper left corner
of cell), thus resetting to new, 

additional observation: on my system calc stopped showing the yellow change
notes somewhere around row 69.000, physical ressources where available (8.9 GB
free mem), are there internal resource limitations?

@all: from the analysis made in #76324 and the behaviour shown for this bug
it's very likely that they have the same root - drawing of boxes, a hidden
drawing layer for copies to clipboard, sort operations instead of lookups,
shallow copies not 'when needed' but 'in preparation' for each and every
element on each and every action, e.g. also on mousemoves not even leaving the
cell, ineffective definition for 'additional info' in the file standard? and
similar annoyances will, of course, affect this sheet as well as sheets with
lots of comments ... but ... they are connected, related, correlated, whatever,
it's not! the same bug - until someone kills it and both symptoms disappear. 

imho it's not! a good practice to 'kill' each and every new report - which
contributes to the knowledge about weaknesses - as 'duplicate' of old bugs
where most users and programmers say 'old stuff' we have lived with that for
years, that can go on ... while others who take a deeper look say: 'That's a
monster, it's better to keep Pandora's box closed'.

we? (you?) do! have some of these monsters in the code (imho (assumption, sorry
Eike) buried under hundreds of 'patches' and tons of plaster that cover up some
of their symptoms) ... after five and more years - imho - it's overdue to
develop a strategy to get rid of them. 

monsters i've seen: 

shared formulae break autocalculate, buggy implementation of shared formulas? 

ineffective handling of comments and similar stuff, big performance impact once
using to much of it, 

reg. 



b.

-- 
You are receiving this mail because:
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.freedesktop.org/archives/libreoffice-bugs/attachments/20191024/79b8adbd/attachment.html>


More information about the Libreoffice-bugs mailing list