Description: Simple uses of VLOOKUP can make Calc busy loop forever Steps to Reproduce: 1. Create a new spreadsheet 2. On Sheet1, insert the following 3 rows 2 columns: colA colB foo 1 bar 2 3. Add Sheet2 and insert the following 2 columns 2 rows: colA colB foo in cell B2 on Sheet2 (under "colB") enter the following formula: =VLOOKUP(A2, Sheet1.A:B, 2, 0) Actual Results: Upon hitting enter Calc will start to busy loop and peg the CPU at 100%. Expected Results: The formula in cell B2 should evaluate to "1". Reproducible: Always User Profile Reset: No Additional Info: Sometimes the formula manages to get evaluated before Calc starts to busy loop. User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_13_3) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/66.0.3355.0 Safari/537.36
Created attachment 140339 [details] Spreadsheet to reproduce the issue The bug can be triggered by entering the formula in cell Sheet2.B2
BTW this looks similar to bug 114509 but I couldn't determine whether it was the same issue. That issue mentions a fairly large input, in my case the input is trivially small. Also if the input is sorted and the last argument passed to VLOOKUP is 1 (or it's omitted), the issue happens anyways. I upgraded to LibreOffice 6 to try to avoid this bug but I'm pretty certain I was running into it on whatever 5.x I was on before (a fairly recent one).
Also I just check as per m.a.riosv's comment in that bug that I do have "Search criteria = and <> must apply to the whole cells" enabled out of the box.
I think its more your formula that give the problem. With =VLOOKUP(A2;$Sheet1.A:B;2;0) i have the correct value of 1 Try to change , to ; and test it again Version: 6.0.1.1 Build ID: SlackBuild for 6.0.1 by Eric Hameleers CPU threads: 8; OS: Linux 4.14; UI render: default; VCL: kde4; Locale: nl-BE (en_US.UTF-8); Calc: group
Hmm, I never thought the coma vs semicolon made a difference, but in any case I tried it and it doesn't work for me. Calc hangs as soon as I hit enter after pasting =VLOOKUP(A2;$Sheet1.A:B;2;0)
(In reply to Benoit Sigoure from comment #5) Would you please copy and paste the content in Help - About LibreOffice dialog? This information may be helpful.
Version: 6.0.1.1 Build ID: 60bfb1526849283ce2491346ed2aa51c465abfe6 CPU threads: 4; OS: Mac OS X 10.13.3; UI render: default; Locale: en-US (en_US.UTF-8); Calc: group threaded
(In reply to Benoit Sigoure from comment #7) This seems to be caused by Calc Threaded Calculation (Calc: group threaded). Would you try to reset your yser profile and see if the issue is gone? Threaded Calculation was disabled by default in Version 6.0 due to bugs. But I see it is enabled in your version, this may be because you haved installed a tesing version of 6.0 which enabled threaded calculation?
Oh I enabled threading yesterday to see if it would make a difference. I had the issue before enabling it. It wasn't enabled out of the box.
(In reply to Benoit Sigoure from comment #9) Do you mean the bug still exists without enableing threaded calculation? Also, does reseting the user profile resolves the issue?
I can reproduce this consistently on a brand new laptop with the latest version of LibreOffice. Version: 6.0.2.1 Build ID: f7f06a8f319e4b62f9bc5095aa112a65d2f3ac89 CPU threads: 4; OS: Mac OS X 10.13.3; UI render: default; Locale: en-US (en_US.UTF-8); Calc: group
Created attachment 140570 [details] macOS report when Calc hangs and is force-quit
Created attachment 140572 [details] CPU sample taken by Activity Monitor while LibreOffice is pegging the CPU
No problem with LibreOffice 6.0.2.1, macOS 10.12.6
No repro with: Version: 6.1.0.0.alpha0+ Build ID: 9122f4598450d8a96e63fb29cc8166a6ae09587a CPU threads: 4; OS: Mac OS X 10.13.3; UI render: default; Locale: fr-FR (fr_FR.UTF-8); Calc: group
I can't repro this either Version: 6.0.2.1 Build ID: f7f06a8f319e4b62f9bc5095aa112a65d2f3ac89 CPU threads: 2; OS: Mac OS X 10.12.6; UI render: default; Locale: en-US (en_US.UTF-8); Calc: group
Benoit: just to be sure, you could try launching in Safe mode to test it: Help - Restart in safe mode and then Continue in safe mode.
(In reply to Buovjaga from comment #17) > Benoit: just to be sure, you could try launching in Safe mode to test it: > Help - Restart in safe mode and then Continue in safe mode. I have set the bug's status to 'NEEDINFO'. Please change it back to 'UNCONFIRMED' if the issue is still present
Dear Bug Submitter, This bug has been in NEEDINFO status with no change for at least 6 months. Please provide the requested information as soon as possible and mark the bug as UNCONFIRMED. Due to regular bug tracker maintenance, if the bug is still in NEEDINFO status with no change in 30 days the QA team will close the bug as INSUFFICIENTDATA due to lack of needed information. For more information about our NEEDINFO policy please read the wiki located here: https://wiki.documentfoundation.org/QA/Bugzilla/Fields/Status/NEEDINFO If you have already provided the requested information, please mark the bug as UNCONFIRMED so that the QA team knows that the bug is ready to be confirmed. Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-NeedInfo-Ping-20181203
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-20190111