After upgrading from 3.5.7 to 220.127.116.11 I noticed that entering data in a 14 sheet spreadsheet was extremely slow. When entering data and pressing ENTER or an arrow key it takes 10+ seconds before the program responds. However I couldn't reproduce this with a simple single sheet spreadsheet. Unfortunately I cannot attach the spreadsheet as it contains confidential data. To test whether the file itself might have become corrupt I have tested this with another spreadsheet, with the same result.
I have tried to open this sheet in 4.0b2 and the behavior is the same. Unworkable slow. A downgrade to 3.5.7 resolved the problem, this version of LO is much more responsive.
System: Win7 64bit, LO: Dutch language.
Hi checkdizz, thanks for reporting.
Do you have conditional formatting in the spreadsheet?.
Yes there is conditional formatting in these spreadsheets. Another feature which might slow things down is the use of array formulas.
Can you try if deleting the conditional formatting solves the issue.
Be care best save the file with other name to avoid damage the original.
If is the same issue was fixed in:
I have tested the conditional formatting, but using LibO-Dev_18.104.22.168.beta2_Win_x86_install_multi instead of 22.214.171.124, because I didn't want to uninstall version 3.5.7. As said in my original post v4b2 has the same behavior.
Indeed when I removed all conditional formatting from all sheets, the slow behavior is resolved. It is worth noting that I need to remove the conditional formatting from all sheets, otherwise the slow behavior remains. This is even the case when entering data on a sheet without any conditional formatting and without any link to sheets with conditional formatting.
Anyway, apparently this is the same bug as 57028. You mention that that bug is solved, but it seems that the solution is not incorporated in v126.96.36.199b2. How can I use the solution? Or should I just wait for the 4.0 final comes out?
Try asking to the developer in the fixed bug if the patch can be incorporated in 3.6.5.
I think will be done after verify the patch is Ok.
*** This bug has been marked as a duplicate of bug 57028 ***