[Libreoffice-bugs] [Bug 76324] CALC becomes very slow with 5000+ comments

bugzilla-daemon at bugs.documentfoundation.org bugzilla-daemon at bugs.documentfoundation.org
Sat Jun 1 06:09:19 UTC 2019


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

--- Comment #73 from b. <newbie-02 at gmx.de> ---
sorry for insisting, and sorry for bad news, but there is still a bug, and it's
bad. 

- there is also something critical in the handling of the bug here, it 'blocks
it from visibility' - 

second problem first, new announcements about variants or 'things left' of
this? bug after changes in versions are thrown out as 'duplicate', while this
bug is kept somewhere between 'low prio', no-repo, delayed, but there is almost
one 'property' of the actual situation - not yet mentioned in this thread -
that hides the problem from being visible to testers, thus collecting
norepo-comments: 

the -problem- seems off in plenty situations after a fresh load of affected
files, it appears / re-appears after the first edit in the sheet and subsequent
autosave. 

the 'issue left', or the problem for me: high cpu load on working in sheets /
files with many comments, 

all sorts of hangs, crashes, 'not repsonding', time and cpu consuming load and
save processes, delays in reaction to mouseclicks, and so on, 

easy test to check: - in windows - 
- produce a file with many cells with data, 
- hover around with the mouse, 
- no cpu load, check with the 'power'? tab (german: Leistung) in the task
manager, 
- make a little change, wait for autosave (you can set it to a short time for
this test, tools - options - load/save - general), 
- hover around with the mouse, 
- nopro, 
- add comments to plenty cells (just copy a not trivial pattern of cells with
comments to a bigger area), 
- hover around, 
- no load, 
- wait for autosave, 
- hover around 
- significant cpu load. 

(set back autosave to a normal value after the test, too many saves might kill
your ssd disk)

(it's not neccessary to click into the cells, just moving the mouse / pointer
(touchpad in my case), (which changes the focus for which cell the comment is
to be evaluated) is enough to produce load)

(it doesn't help that the load is 'only' 12 to 15 percent on powerful systems,
it's the difference from being 0 to 1 percent before autosave what says
'problem') 

(also 'easements' like saving in 'fods' format (it has significantly mitigated
the problem in some situations) or 'restart in safe mode' (no difference on my
tests) do not bring away the problem) 

is this 'pinpointing' helpful to identify the source of the problem? 

shall i open a new bug for this special scenario and is there hope it will not
be closed as duplicate? 

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/20190601/183d4ab6/attachment-0001.html>


More information about the Libreoffice-bugs mailing list