Bug 76447 - MULTIPLE.OPERATIONS() shows wrong results when some internal limit is reached
Summary: MULTIPLE.OPERATIONS() shows wrong results when some internal limit is reached
Status: NEW
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Calc (show other bugs)
(earliest affected) release
Hardware: All All
: medium minor
Assignee: Not Assigned
Depends on:
Blocks: Calc-Function
  Show dependency treegraph
Reported: 2014-03-21 12:29 UTC by lactea
Modified: 2022-03-29 03:59 UTC (History)
4 users (show)

See Also:
Crash report or crash signature:
Regression By:

To make multple.operations work, please delete all content below row 396 and enter 1 in V397. (516.17 KB, application/vnd.oasis.opendocument.spreadsheet)
2014-03-21 12:29 UTC, lactea
working example (60.96 KB, application/vnd.oasis.opendocument.spreadsheet)
2014-03-21 12:40 UTC, lactea
broken example (516.17 KB, application/vnd.oasis.opendocument.spreadsheet)
2014-03-21 12:42 UTC, lactea
Minimal broken example. (436.49 KB, application/vnd.oasis.opendocument.spreadsheet)
2014-10-08 18:04 UTC, lactea

Note You need to log in before you can comment on or make changes to this bug.
Description lactea 2014-03-21 12:29:20 UTC
Created attachment 96159 [details]
To make multple.operations work, please delete all content below row 396 and enter 1 in V397.

multiple.operations is not working for long calculations. Only the very first entry is calculated and the rest is being copied from the first cell. Consequently, all results are the same.
This appears to happen when more then 393 rows in the attached example are calculated. Suspecting hardcoded limitation. Find both an working and broken calculation attached.
Tested on Linux and Windows XP running and (at least).
Check also
and the attached file. [To make multple.operations work, please delete all content below row 396 and enter 1 in V397.]
Comment 1 lactea 2014-03-21 12:40:09 UTC
Created attachment 96160 [details]
working example

Note different values in the cross-table. Working as supposed with a limited number of calculations.
Comment 2 lactea 2014-03-21 12:42:21 UTC
Created attachment 96161 [details]
broken example

Note that those values in the cross-table are all the same.
Comment 3 mahfiaz 2014-03-21 18:54:49 UTC
On 64-bit Linux having 824th row as the last one with data works, adding one row breaks it (see the non-working documents in ask.libo.org question, referenced in the first post).
Comment 4 Owen Genat (retired) 2014-03-21 23:28:39 UTC
As a result of comment 3, and this comment, confirmed. Status set to NEW. The only difference here under Debian 7 x86_64 using:

- v4.1.4.2 Build ID: 0a0440ccc0227ad9829de5f46be37cfb6edcf72

... Crunchbang 11 x86_64 using:

- v4.2.2.1 Build ID: 3be8cda0bddd8e430d8cda1ebfd581265cca5a0f

... is that both the working and broken examples change state from working to broken at row 396/397 (instead of row 824/825 as reported in comment 3 and the AskLO answer).
Comment 5 lactea 2014-10-08 17:45:38 UTC
Tested (among other versions) on latest Issue still exists.
Comment 6 lactea 2014-10-08 18:04:08 UTC
Created attachment 107572 [details]
Minimal broken example.

A minimum example. Just 2 input cells, one output cell and four columns of data.
Comment 7 QA Administrators 2016-02-21 08:34:17 UTC Comment hidden (obsolete)
Comment 8 mahfiaz 2016-04-23 11:00:57 UTC
Still an issue with the current dev build:

Build ID: b19ac3c4c6b4a41a1f3acac68b299fd676428a87
CPU Threads: 4; OS Version: Linux 4.2; UI Render: default; 
TinderBox: Linux-rpm_deb-x86_64@70-TDF, Branch:master, Time: 2016-04-21_08:41:0
Comment 9 Vianney Stroebel 2016-11-04 13:07:09 UTC
This bug might be related to https://bugs.documentfoundation.org/show_bug.cgi?id=103701
Comment 10 Xisco Faulí 2017-06-12 11:28:24 UTC
Changing version back to the earliest affected version.
Comment 11 QA Administrators 2018-06-13 02:35:57 UTC Comment hidden (obsolete)
Comment 12 xyhausen 2020-03-28 20:17:50 UTC
Still reproducible with "broken example"

Version: (x64)
Build-ID: 4e471d8c02c9c90f512f7f9ead8875b57fcb1ec3
CPU-Threads: 2; BS: Windows 10.0 Build 18362; UI-Render: Standard; VCL: win; 
Gebietsschema: en-GB (de_DE); UI-Sprache: de-DE
Comment 13 QA Administrators 2022-03-29 03:59:46 UTC
Dear lactea,

To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year.

There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present.

If you have time, please do the following:

Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/

If the bug is present, please leave a comment that includes the information from Help - About LibreOffice.
If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice.

Please DO NOT

Update the version field
Reply via email (please reply directly on the bug tracker)
Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not 
appropriate in this case)

If you want to do more to help you can test to see if your issue is a REGRESSION. To do so:
1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from https://downloadarchive.documentfoundation.org/libreoffice/old/

2. Test your bug
3. Leave a comment with your results.
4a. If the bug was present with 3.3 - set version to 'inherited from OOo';
4b. If the bug was not present in 3.3 - add 'regression' to keyword

Feel free to come ask questions or to say hello in our QA chat: https://web.libera.chat/?settings=#libreoffice-qa

Thank you for helping us make LibreOffice even better for everyone!

Warm Regards,
QA Team