Bug 141920 - Calculation formula crashed after entering $ for locked cell reference
Summary: Calculation formula crashed after entering $ for locked cell reference
Status: RESOLVED INSUFFICIENTDATA
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Calc (show other bugs)
Version:
(earliest affected)
7.0.5.2 release
Hardware: ARM macOS (All)
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2021-04-26 18:41 UTC by Timo Kytta
Modified: 2021-10-25 18:40 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 Timo Kytta 2021-04-26 18:41:12 UTC
I assumed locking cell reference in a formula works similar way to Excel i.e. entering '$' character to cell address' (for example '$C$2'). When I created a formula, added those $-characters and hit enter, the whole LibreOffice crashed immediately.

I'm using Macbook Air M1 with Big Sur 11.2.3
Comment 1 Ming Hua 2021-04-26 21:31:43 UTC
(In reply to Timo Kytta from comment #0)
> I'm using Macbook Air M1 with Big Sur 11.2.3
I assume you downloaded LibreOffice from the official https://www.libreoffice.org/download/download/ site, or Apple's App Store?

AFAIK those two places don't provide build for ARM64 CPU architecture yet (and your Macbook M1 have one), so are you using the Rosetta-equivalent to run an Intel-based LibreOffice App on your Macbook M1?

Just to be sure, can you paste the detailed version information here?  It's located in menu "LibreOffice > About LibreOffice" (or some other menu > About LibreOffice), and there is a copy button (after "Version Information") in the pop-up dialog that you can use to copy the needed information to the clipboard.  Like this:

Version: 7.0.6.1 (x64)
Build ID: 334c13825bee34d130f569ff5912aec5389765c1
CPU threads: 2; OS: Windows 10.0 Build 19041; UI render: default; VCL: win
Locale: zh-CN (zh_CN); UI: en-US
Calc: threaded
Comment 2 Timo Kytta 2021-04-27 04:45:57 UTC
Yes, it's coming from the LibreOffice site.

Version:
Version: 7.0.5.2
Build ID: 64390860c6cd0aca4beafafcfd84613dd9dfb63a
CPU threads: 8; OS: Mac OS X 10.16; UI render: GL; VCL: osx
Locale: fi-FI (fi_FI.UTF-8); UI: en-US
Calc: threaded

ARM-selection was then most probably wrong... I assumed that M1 counts as ARM in that form. And yes, via Rosetta2 as there's no M1-LibreOffice yet.

--

I planned to redo the crash and add a screen shot here, but now that I did the same formula on an empty Calc sheet, it didn't crash and $-char in calculation worked as I assumed it to work. So this bug became much harder to debug since I can't say what exactly caused it.
Comment 3 Xisco Faulí 2021-04-27 07:44:25 UTC
Thank you for reporting the bug. Please attach a sample document, as this makes it easier for us to verify the bug. 
I have set the bug's status to 'NEEDINFO'. Please change it back to 'UNCONFIRMED' once the requested document is provided.
(Please note that the attachment will be public, remove any sensitive information before attaching it. 
See https://wiki.documentfoundation.org/QA/FAQ#How_can_I_eliminate_confidential_data_from_a_sample_document.3F for help on how to do so.)
Comment 4 Ming Hua 2021-04-27 08:52:29 UTC
(In reply to Timo Kytta from comment #2)
> Yes, it's coming from the LibreOffice site.
> 
> Version:
> Version: 7.0.5.2
> Build ID: 64390860c6cd0aca4beafafcfd84613dd9dfb63a
> CPU threads: 8; OS: Mac OS X 10.16; UI render: GL; VCL: osx
> Locale: fi-FI (fi_FI.UTF-8); UI: en-US
> Calc: threaded
Thanks for the feedback.

> ARM-selection was then most probably wrong... I assumed that M1 counts as
> ARM in that form. And yes, via Rosetta2 as there's no M1-LibreOffice yet.
The CPU selection is fine.  After all, the Rosetta situation on macOS is a rather special case, and as long as you've given clear information, we can leave it as is.

> I planned to redo the crash and add a screen shot here, but now that I did
> the same formula on an empty Calc sheet, it didn't crash and $-char in
> calculation worked as I assumed it to work. So this bug became much harder
> to debug since I can't say what exactly caused it.
This however is a bigger problem.  As Xisco said above, if there is no sample document or easy steps to reproduce, developers can't do much about this bug.

So either you can find a way to reproduce, or someone else reports the same problem.  Otherwise, we'll have to eventually close the bug.  You can always easily reopen it and provide more information once you find a way to reliably reproduce it.
Comment 5 QA Administrators 2021-10-25 03:56:21 UTC Comment hidden (obsolete)
Comment 6 Timo Kytta 2021-10-25 18:40:07 UTC
This hasn't happened after this incident, so I will close this.