Bug 126228 - calc crashes if "SUMIFS" is used in formular
Summary: calc crashes if "SUMIFS" is used in formular
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Calc (show other bugs)
(earliest affected) release
Hardware: x86-64 (AMD64) Linux (All)
: medium normal
Assignee: Not Assigned
Keywords: filter:ods
Depends on:
Blocks: Calc-Function
  Show dependency treegraph
Reported: 2019-07-04 13:28 UTC by markus
Modified: 2020-02-09 03:42 UTC (History)
2 users (show)

See Also:
Crash report or crash signature:

screenshot that shows formular and error (140.97 KB, image/png)
2019-07-04 13:28 UTC, markus
tests SUMIFS (156.61 KB, application/vnd.oasis.opendocument.spreadsheet)
2019-07-04 16:01 UTC, markus

Note You need to log in before you can comment on or make changes to this bug.
Description markus 2019-07-04 13:28:24 UTC
Created attachment 152562 [details]
screenshot that shows formular and error


i am encountering a _M_fill_index - crash whenever i try to use SUMIFS in a formular.

pls verify attached screenshot.

while SUMIF is working correctly, i could not find a way to use SUMIFS.


Comment 1 Xisco Faulí 2019-07-04 13:50:26 UTC
Thank you for reporting the bug. Please attach a sample document, as this makes it easier for us to verify the bug. 
(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.)

I have set the bug's status to 'NEEDINFO'. Please change it back to 'UNCONFIRMED' once the requested document is provided.
Comment 2 markus 2019-07-04 15:41:36 UTC
just verified, same bug is also present in windows using lo 2.2.5
Comment 3 Xisco Faulí 2019-07-04 15:46:48 UTC
Hi markus,
Could you please attach a document to reproduce the issue or indicate the steps to reproduce it ?
Comment 4 markus 2019-07-04 15:59:00 UTC
hmm....  ?

while compiling a sample document, i found, the wizard replaces ";" with "," - seems to work now.
Comment 5 markus 2019-07-04 16:01:13 UTC
Created attachment 152564 [details]
tests SUMIFS
Comment 6 markus 2019-07-04 16:10:44 UTC
works in attached document, but not in the original one...
Comment 7 QA Administrators 2019-07-05 02:46:36 UTC Comment hidden (obsolete)
Comment 8 Xisco Faulí 2019-07-05 10:05:52 UTC
I can't reproduce it in

Build ID: d62f6b7d40284b2e41831376e5388711ab6250f3
CPU threads: 4; OS: Linux 4.15; UI render: default; VCL: gtk3; 
Locale: ca-ES (ca_ES.UTF-8); UI-Language: en-US
Calc: threaded

(In reply to markus from comment #6)
> works in attached document, but not in the original one...

Could you please attach the original one ?
Comment 9 BogdanB 2019-07-12 18:04:18 UTC
No crash on
Build ID: 1ec314fa52f458adc18c4f025c545a4e8b22c159
CPU threads: 4; OS: Linux 4.15; UI render: default; VCL: gtk3; 
Locale: ro-RO (ro_RO.UTF-8); UI-Language: en-US
Calc: threaded
Comment 10 QA Administrators 2020-01-09 03:37:30 UTC Comment hidden (obsolete)
Comment 11 QA Administrators 2020-02-09 03:42:43 UTC
Dear markus,

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