Hi, Got 2 crash reports from crashes while manipulating pivot charts this morning. crashreport.libreoffice.org/stats/crash_details/c1747de0-3a1b-43a1-951a-7cdee63b1a39 crashreport.libreoffice.org/stats/crash_details/bbbbd7d0-ba2c-4104-b6a8-dba7419ce505 Regards, Eric Ficheux
Could you: 1) attach an example file (have in mind that any attachment is automatically made public so remove any confidential/private part from it) 2) indicate step by step process to reproduce this?
Hi Julien, As for many other crashes, those two are the random kind. I tried to reproduce them but didn't succeed. Hope the crash report is enough to investigate. Regards, Eric Ficheux
Adding Tomaz Vajngerl since he's the one of implemented the functionality. @Tomaz, are the crashreports enough for you to know where the crash might be? otherwise, we will need the steps to reproduce the crash...
Dear Reporter, Could you please attach the document used at the time LibreOffice crashed ?
Hi Xisco, Don't have the exact same document anymore. I modified it, thought the crash dump would be enough to investigate. Will do some more tests and keep the documents, Regards, Eric
Encountered crash creating a new pivot table and a new pivot chart http://crashreport.libreoffice.org/stats/crash_details/31496aaa-5fd0-44a6-aab0-9574b3ebe5f0 Attached test document, hope this helps
Created attachment 134593 [details] Test file
Tried on Windows-10 (1607 dev edition) with LO 5.4.0.1 with the attached document. Created new pivot table and pivot chart but no crash observed. Also tried changing some data in the sheet1 and refreshed pivot table/pivot chart, still no crash.
Eric, Could you please provide a list of concrete steps to trigger the crash? Something like: 1) Open the attached bug document. 2) Click here. 3) Type that. and so on. :-) I guess the crash only happens when you create a given pivot table with given parameters and you create a pivot chart with specific parameters, not in general. It may be hard to guess what are these exact parameters. Thanks!
*** This bug has been marked as a duplicate of bug 109523 ***