Bug 96477 - vlookup array selection with mouse hanged Calc
Summary: vlookup array selection with mouse hanged Calc
Status: RESOLVED INSUFFICIENTDATA
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Calc (show other bugs)
Version:
(earliest affected)
unspecified
Hardware: All All
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2015-12-14 09:44 UTC by Ari Latvala
Modified: 2017-09-29 08:54 UTC (History)
4 users (show)

See Also:
Crash report or crash signature:


Attachments
test file (260.44 KB, application/zip)
2015-12-17 13:15 UTC, Ari Latvala
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Ari Latvala 2015-12-14 09:44:48 UTC
Running LibreOffice 5.0.3.2 on Linux RHEL 6.7 64-bit.

Had a csv imported file with 63193 rows and 15 columns, last one of them on date format. Then added a second sheet for formlulas and used vlookup. Now trying to select array with mouse to include whole sheet ended up with total hang. Kept mouse button pressed and cursor positioned for max speed somewhere near to row 40000, then moved cursor but kept left button still pressed to stop scrolling but nothing happened. Waited till the selected area was near 60000, then released also the mouse button but still nothing happened, selected area just kept growing and growing. Waited untill well over 110 000 rows were alreay selected, then tried to switch focus to other windows but also on those mouse was not responding, only keyboard was functional. End result much later was non-responding Calc, which I had to force terminate.
Comment 1 raal 2015-12-14 20:17:33 UTC
Hello,
could you attach a test file? Thanks
Comment 2 Buovjaga 2015-12-17 12:44:28 UTC
Can we have a test file for Christmas?

Set to NEEDINFO.
Change back to UNCONFIRMED after you have provided the Christmas present.
Comment 3 Ari Latvala 2015-12-17 13:15:00 UTC
Created attachment 121364 [details]
test file

When selecting array with mouse for vlookup at "List" tab (all data on "Inventory" tab, as shown on example at B2 cell), LibreOffice 5.0.3 hangs to the point that only Alt+F4 and Force Quite with keyboard works. Mouse clicks don't work any more for any application on Linux RHEL 6.7 64-bit. Machine is Lenovo W530.
Comment 4 Buovjaga 2015-12-21 17:54:37 UTC
(In reply to Ari Latvala from comment #3)
> Created attachment 121364 [details]
> test file
> 
> When selecting array with mouse for vlookup at "List" tab (all data on
> "Inventory" tab, as shown on example at B2 cell), LibreOffice 5.0.3 hangs to
> the point that only Alt+F4 and Force Quite with keyboard works. Mouse clicks
> don't work any more for any application on Linux RHEL 6.7 64-bit. Machine is
> Lenovo W530.

No problem here.

Win 7 Pro 64-bit, Version: 5.0.4.2 (x64)
Build ID: 2b9802c1994aa0b7dc6079e128979269cf95bc78
Locale: fi-FI (fi_FI)

Version: 5.2.0.0.alpha0+
Build ID: 014633f83e44ae8ba33087b6f38e8e253e281969
CPU Threads: 4; OS Version: Windows 6.1; UI Render: default; 
TinderBox: Win-x86@62-merge-TDF, Branch:MASTER, Time: 2015-12-15_06:21:44
Locale: fi-FI (fi_FI)

Ubuntu 15.10 64-bit 
Version: 5.0.3.2
Build ID: 1:5.0.3~rc2-0ubuntu1
Locale: en-US (en_US.UTF-8)
Comment 5 Ari Latvala 2015-12-21 21:38:48 UTC
I have no problems on Windows 7 with 5.0.4.2 but under 64-bit Linux problem happens everytime on LibreOffice 5.0.3.2, when using mouse to select area from the first cell on the left top corner to the lowest at the bottom right. Sounds like some sort of buffer overrun problem but is it on mouse driver, OS level or on LibreOffice, I do not know.

Using keyboard works just nice for area selection, so it is purely mouse related problem. Selection takes several minutes with mouse because of the slow scroll. With keyboard selection is almost instant.
Comment 6 Buovjaga 2015-12-22 09:00:17 UTC
What is your desktop environment on RHEL? Gnome 3?
Comment 7 Ari Latvala 2015-12-22 10:17:49 UTC
Red Hat Enterprise Linux Workstation, release 6.7 (Santiago)
Kernel Linux 2.6.32-573.8.1.el6.x86_64
GNOME 2.28.2

RAM 16GB, CPU i7-3720QM @ 2.60GHz
Comment 8 Buovjaga 2015-12-22 10:26:52 UTC
(In reply to Ari Latvala from comment #7)
> Red Hat Enterprise Linux Workstation, release 6.7 (Santiago)
> Kernel Linux 2.6.32-573.8.1.el6.x86_64
> GNOME 2.28.2
> 
> RAM 16GB, CPU i7-3720QM @ 2.60GHz

Any plans to upgrade to RHEL 7? :)
Comment 9 Ari Latvala 2015-12-22 11:11:21 UTC
RHEL 7.2 for company machines just released, not sure yet, when I will take the pain to rebuild the machine though.
Comment 10 Aron Budea 2017-01-28 04:16:14 UTC
Ari, did you get a chance to check with an updated version/system?
Comment 11 Ari Latvala 2017-02-05 07:50:19 UTC
(In reply to Aron Budea from comment #10)
> Ari, did you get a chance to check with an updated version/system?

Won't happen yet, probably sometime in April/May will get new machine with RHEL 7.3.
Comment 12 QA Administrators 2017-08-30 19:27:00 UTC Comment hidden (obsolete)
Comment 13 QA Administrators 2017-09-29 08:54:01 UTC
Dear Bug Submitter,

Please read this message in its entirety before proceeding.

Your bug report is being closed as INSUFFICIENTDATA due to inactivity and
a lack of information which is needed in order to accurately
reproduce and confirm the problem. We encourage you to retest
your bug against the latest release. If the issue is still
present in the latest stable release, we need the following
information (please ignore any that you've already provided):

a) Provide details of your system including your operating
   system and the latest version of LibreOffice that you have
   confirmed the bug to be present

b) Provide easy to reproduce steps – the simpler the better

c) Provide any test case(s) which will help us confirm the problem

d) Provide screenshots of the problem if you think it might help

e) Read all comments and provide any requested information

Once all of this is done, please set the bug back to UNCONFIRMED
and we will attempt to reproduce the issue. Please do not:

a) respond via email 

b) update the version field in the bug or any of the other details
   on the top section of our bug tracker

Warm Regards,
QA Team

MassPing-NeedInfo-20170929