Bug 103533 - Fileopen dump using Procdump with specific XLSX, no recovery window
Summary: Fileopen dump using Procdump with specific XLSX, no recovery window
Status: NEW
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Calc (show other bugs)
(earliest affected) release
Hardware: All Windows (All)
: lowest minor
Assignee: Not Assigned
Keywords: filter:xlsx, haveBacktrace
Depends on:
Blocks: XLSX
  Show dependency treegraph
Reported: 2016-10-27 10:23 UTC by Timur
Modified: 2021-07-15 10:46 UTC (History)
3 users (show)

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

Test XLXS (2.22 MB, application/vnd.openxmlformats)
2016-10-27 10:24 UTC, Timur
Test XLXS backtrace (15.12 KB, text/plain)
2016-10-27 10:24 UTC, Timur
Test XLXS backtrace with LO 6.4+ (11.94 KB, text/plain)
2019-07-08 06:39 UTC, Timur

Note You need to log in before you can comment on or make changes to this bug.
Description Timur 2016-10-27 10:23:58 UTC
On fileopen dump with specific XLSX, and prodcump on, I get dump. There's no recovery window and file opens. 
Tested with LO 4.1, 5.1 and 5.3+ master in Windows. Doesn't happen with OO and it doesn't ask to update links.

Steps to Reproduce:
1. Open fresh LO (or close all and open)
2. Get procdump running
3. Fileopen attached XLSX

Actual Results:  
Hung window and dump count reached.

Expected Results:
dump count not reached

Reproducible: Always

User Profile Reset: Not related.

Additional Info:
I had some other problems with this file I can't reproduce now, like hangs on sheet copy or table copy.

User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:38.0) Gecko/20100101 Firefox/38.0
Comment 1 Timur 2016-10-27 10:24:39 UTC
Created attachment 128299 [details]
Comment 2 Timur 2016-10-27 10:24:59 UTC Comment hidden (obsolete)
Comment 3 m.a.riosv 2016-10-27 22:52:30 UTC Comment hidden (obsolete)
Comment 4 Timur 2016-10-28 16:32:38 UTC
(In reply to m.a.riosv from comment #3)
> Links are in Chart's data.
> Ask for update it's an option in Menu/Tools/Calc/General - Updating.
Thank you. But it's not a solution to the bug, right. If you're on Linux please check bug under See Also.
Comment 5 Buovjaga 2016-11-16 11:04:28 UTC
Yep, I get a dump.

For testers: https://wiki.documentfoundation.org/How_to_get_a_backtrace_with_WinDbg#Producing_a_mini_dump

Win 7 Pro 64-bit Version:
Build ID: c5f5b3e5334c52502c1de28828a44ad469c68850
CPU Threads: 4; OS Version: Windows 6.1; UI Render: default; Layout Engine: new; 
TinderBox: Win-x86@39, Branch:master, Time: 2016-11-14_06:24:21
Locale: fi-FI (fi_FI); Calc: group
Comment 6 Eike Rathke 2016-12-14 22:27:37 UTC
Doesn't crash for me, Linux master, 5-3 and 5.2.4
Comment 7 Eike Rathke 2016-12-15 00:11:21 UTC
This is a pathological document anyway, for why see comment https://bugs.documentfoundation.org/show_bug.cgi?id=103543#c6
Thousands of hidden drawing layer objects on some sheet(s).
Maybe on Windows some memory or structures are exhausted.
Comment 8 QA Administrators 2018-07-03 02:38:29 UTC Comment hidden (obsolete)
Comment 9 Timur 2018-07-05 07:51:29 UTC
Still dump in 6.2+.
Document is wrong as Eike explained. 
But I guess we shouldn't have dump.
Comment 10 QA Administrators 2019-07-06 02:47:33 UTC Comment hidden (obsolete)
Comment 11 Timur 2019-07-08 06:39:49 UTC Comment hidden (obsolete)
Comment 12 QA Administrators 2021-07-08 03:42:25 UTC Comment hidden (obsolete)
Comment 13 Timur 2021-07-15 10:46:31 UTC
Repro 7.3+. Lowest.