Summary: | Crash if pasting/copying calc cells with comments (5000 lines) | ||
---|---|---|---|
Product: | LibreOffice | Reporter: | perie_gut |
Component: | Calc | Assignee: | Not Assigned <libreoffice-bugs> |
Status: | RESOLVED DUPLICATE | ||
Severity: | normal | CC: | ilmari.lauhakangas, newbie-02, telesto |
Priority: | medium | ||
Version: | 6.0.0.0.beta2 | ||
Hardware: | All | ||
OS: | All | ||
Whiteboard: | |||
Crash report or crash signature: | Regression By: |
Description
perie_gut
2017-12-10 03:55:30 UTC
Version: 6.0.0.0.beta2 Build ID: 13edaaa12f25de343fce136064e27da66c1c4fa4 CPU threads: 4; OS: Windows 10.0; UI render: default; Locale: en-US (en_US); Calc: CL no repro job finished in 48seconds, saving/closing is a bit slow Version: 6.0.0.0.beta1+ Build ID: bfe2fb8ceed6643574010bf7b40f04d149f0fd6d CPU threads: 8; OS: Linux 4.9; UI render: default; VCL: kde4; Locale: nl-BE (en_US.UTF-8); Calc: group threaded homebuild 07/12/2017 Version: 6.1.0.0.alpha0+ Build ID: f7c841f56f7c1e9b7757ba3a5c22ab499ac1a48e CPU threads: 8; OS: Linux 4.9; UI render: default; VCL: kde4; TinderBox: Linux-rpm_deb-x86_64@70-TDF, Branch:master, Time: 2017-12-01_00:15:50 Locale: nl-BE (en_US.UTF-8); Calc: group threaded Yep, let's dupe. *** This bug has been marked as a duplicate of bug 76324 *** @Xavier: did you A) copy the commented cell from col A to col G? with col B to F left empty, thus producing 10k of commented cells, or did you B) copy the commented cells into the range! Ax:Gx? with also copies in Bx to Fx? resulting in 35k of commented cells. my best result for the copy to 5k rows with A): 14 seconds with LO ver 6.2.8.2 win, while B) with - only - 3,5 times the amount of comments took 2:12 minutes, there is a 'non linear' effect from the amount of comments. that while all linux versions showed much worse performance! the good performance of ver 6.2 is fading out, 7.0.0.0.a0+ took 3:50 minutes with var. B) to become ready to click on a new cell, and afterwards took between 1 and 3:30 minutes to react (change the focus to that cell) after a click on a cell ... unusable. - good? performance ... no ... 'a little less bad', good would be if commented cells could keep up with the processing speed of normal cells, it takes less than a second to copy two cells, one with 'a' and one with 'test' in it, to 70k cells (A1:N5000), thus we can say storing and handling of information in comments is very inefficient at all - 6.2.8.2 - win!!! - stays 'responsive' also with 35k of commented cells, that's why i'm using it. reg. b. |