https://issues.apache.org/ooo/show_bug.cgi?id=123698
Bug ID: 123698
Issue Type: DEFECT
Summary: Lg files with thousands of calcs often "Not
Responding" & "adapting row height"
Product: Calc
Version: 3.4.1
Hardware: PC
OS: Windows 8
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: editing
Assignee: [email protected]
Reporter: [email protected]
CC: [email protected]
I have this problem with ALL of my large calc files. None of them have macros
(that I know of). They each have 4 - 6 sheets with each sheet having 100 or so
rows & maybe 30 columns & >50% of the cells are calculations, but not macros.
I have this problem with OO calc v3.4. I never had it with OO calc v2.4.
The files open instnatly, but the first time I change any cell, they go to
"Not responding" (in the top msg bar) &
"adapting row height" (in the bottom msg bar).
They take over 30 seconds to save.
After the first mini-crash after the first cell change, they don't seem to go
into spasm after EVERY cell change but they do after most cell changes.
I tried the User profile stuff & it is no help.
I tried turning off auto-calc & so far it doesn't seem to help any.
I even tried setting all the row heights to default, but that didn't help.
I have also described other bizarre "row height"-related happenings in a forum
thread. (for example, when I copy the contents of a cell to the cell in SAME
ROW but next column, the row height visibly increases, even though I just
copied from the SAME ROW.)
I think it is a problem with the "lock files" in v3.4. v2.4 had no lock files.
Some things I have seen make me think the combination of thousands of calcs &
any need for the file to even think about row hieghts causes issues with
updating the lock file.
OO should take seriously the reality that with all the same calc files but on a
much slower PC, I never have this problem using v2.4. There is clearly a bug in
v3.4. Has it been admitted &/or addressed in v4? Given that v3.4 is a worse
experience than v2.4 is, I won't go to v4 w/o clear knowledge that this has
been fixed.
--
You are receiving this mail because:
You are on the CC list for the bug.
You are the assignee for the bug.
You are watching all bug changes.
