Bug 109079 - Entering data into cells is delayed by up to 5 seconds
Summary: Entering data into cells is delayed by up to 5 seconds
Status: RESOLVED WORKSFORME
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Chart (show other bugs)
Version:
(earliest affected)
3.4.1 release
Hardware: All Windows (All)
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2017-07-12 11:02 UTC by Martin
Modified: 2018-01-09 11:22 UTC (History)
2 users (show)

See Also:
Crash report or crash signature:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Martin 2017-07-12 11:02:33 UTC
Description:
When I enter data nothing appears in either the command line or the selected cell for up to 5 seconds. There is a similar delay when I select a new cell or perform a calculation. This makes the software very slow and frustrating to use.

This only happens on newly created spreadsheets. Editing spreadsheets created under previous releases is normal.

Restarting in safe mode returns behaviour to normal.

Resetting user profile returns behaviour to normal on the first occasion Calc is started. Thereafter the fault returne

Steps to Reproduce:
1.See description
2.
3.

Actual Results:  
See description

Expected Results:
See description


Reproducible: Always

User Profile Reset: Yes (see description)

Additional Info:


User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:54.0) Gecko/20100101 Firefox/54.0
Comment 1 Buovjaga 2017-08-07 15:43:21 UTC
Please copy and paste here the contents of your Help - About. This allows us to know more about your system.

Do you have extensions installed?

Set to NEEDINFO.
Change back to UNCONFIRMED after you have provided the information.
Comment 2 Martin 2017-08-31 21:39:48 UTC
Version: 5.3.4.2
Build ID: f82d347ccc0be322489bf7da61d7e4ad13fe2ff3
CPU Threads: 8; OS Version: Windows 6.2; UI Render: default; Layout Engine: new; 
Locale: en-GB (en_GB); Calc: group

Extension Solver for nonlinear programming 0.9 - (bundled with libreoffice)
Comment 3 Buovjaga 2017-09-07 17:09:34 UTC
Does the same happen with a fresh master build (installs separately): https://dev-builds.libreoffice.org/daily/master/Win-x86_64@62-TDF/current/
Comment 4 Xisco Faulí 2017-10-31 17:58:40 UTC Comment hidden (obsolete)
Comment 5 Martin 2017-11-01 17:24:10 UTC
Couldn't access masterbuild quoted (404 error)

I have installed:

Version: 6.0.0.0.alpha1+ (x64)
Build ID: dae6ba564fcf20299b7a560aeb346efc84364d41
CPU threads: 8; OS: Windows 10.0; UI render: GL; 
TinderBox: Win-x86_64@42, Branch:master, Time: 2017-11-01_01:54:14
Locale: en-GB (en_GB); Calc: CL

This appears to behave perfectly with no delay on data entry
Comment 6 Buovjaga 2017-11-01 17:30:19 UTC
(In reply to Martin from comment #5)
> This appears to behave perfectly with no delay on data entry

Sounds good. I wonder if it's related to spellchecking? Does your stable version spellcheck while typing?
Comment 7 Martin 2017-11-01 18:30:02 UTC
Yes I normally run automatic spell check. However, I have just tried unchecking all the spell checking options and restarting the program (this is 5.4.3.2 again) and it makes no difference. 

Text with deliberate misspellings was accepted without underscore after a short delay.

I tried entering a column of random numbers, moving the cursor from cell to cell and typing. The cells were not highlighted as I selected them.  Nothing happened for several seconds then all the numbers appeared as entered.

Strange data latency is still with us - but apparently only in the one version.

Apologies for the delay in answering your previous request. It arrived at a busy time and then fell off the end of the to-do list.
Comment 8 Buovjaga 2017-11-02 10:10:17 UTC
Ok, so 5.4.x is bad no matter what and 6.0 works fine. The stable release of 6.0 is still some months in the future: https://wiki.documentfoundation.org/ReleasePlan/6.0

Yet, if you are happy, you can close this report as RESOLVED WORKSFORME.
Comment 9 Xisco Faulí 2018-01-09 11:22:59 UTC
Closing as RESOLVED WORKSFORME as per comment 8. Please, put it back to UNCONFIRMED if the issue is still reproducible in master