Bug 124766 - Exported pivot table crashes Excel when modifying years filter
Summary: Exported pivot table crashes Excel when modifying years filter
Status: NEW
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Calc (show other bugs)
(earliest affected)
Hardware: All All
: medium normal
Assignee: Not Assigned
Keywords: filter:xlsx
Depends on:
Blocks: XLSX-Corrupted Pivot-Table-XLSX
  Show dependency treegraph
Reported: 2019-04-16 08:49 UTC by Mike Kaganski
Modified: 2023-02-18 03:24 UTC (History)
2 users (show)

See Also:
Crash report or crash signature:

sc/qa/unit/data/xlsx/pivot-table/shared-dategroup.xlsx (17.13 KB, application/vnd.openxmlformats-officedocument.spreadsheetml.sheet)
2019-04-16 08:49 UTC, Mike Kaganski

Note You need to log in before you can comment on or make changes to this bug.
Description Mike Kaganski 2019-04-16 08:49:22 UTC
Created attachment 150781 [details]

In current master (after https://git.libreoffice.org/core/+/b082998401e37e6c7534906601bc481423a6ded0):

1. Open the attachment (out unit test document) and re-save back to XLSX;
2. Open the result in Excel 2016;
3. Clicking the drop-down button next to "a" in any of the pivot tables;
4. Apply any modification to the list (like unchecking "1965") and confirm OK.
=> Excel crashes (just disappears without error messages; next launch shows recovery panel).

Refreshing pivots in Excel before operation prevents crash.

This is not strictly a regression, since it is likely related to the new functionality (export of group fields) previously missing in LO XLSX export filter.
Comment 1 Roman Kuznetsov 2019-04-16 09:12:50 UTC
confirm for MS Excel 2010 after resave to XLSX in

Build ID: 3083fe569f96bf0289da1e9d0ef7da15ab22e2f6
CPU threads: 4; OS: Windows 6.1; UI render: default; VCL: win; 
TinderBox: Win-x86@42, Branch:master, Time: 2019-04-16_01:39:55
Locale: ru-RU (ru_RU); UI-Language: en-US
Calc: threaded
Comment 2 Xisco Faulí 2019-08-07 13:23:56 UTC
Hi Mike,
Is the the same as bug 126748 ?
Comment 3 Xisco Faulí 2019-08-07 13:24:19 UTC
(In reply to Xisco Faulí from comment #2)
> Hi Mike,
> Is the the same as bug 126748 ?

same root cause*
Comment 4 Mike Kaganski 2019-08-07 13:27:52 UTC
(In reply to Xisco Faulí from comment #3)

No, the root causes are completely different. Yes, they both are related to the same commit.
Comment 5 Roman Kuznetsov 2021-02-17 11:27:56 UTC
still repro in

Version: (x64) / LibreOffice Community
Build ID: 2c8ffa41ec8e1ab2af95d5e033a445c17d29cf5a
CPU threads: 4; OS: Windows 10.0 Build 18363; UI render: Skia/Raster; VCL: win
Locale: ru-RU (ru_RU); UI: ru-RU
Calc: threaded
Comment 6 QA Administrators 2023-02-18 03:24:11 UTC
Dear Mike Kaganski,

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