Bug 77501

Summary: FILESAVE/FILEOPEN: LibreOffice/OSX Spreadsheet crashes on document written by itself in xlsm format
Product: LibreOffice Reporter: printcsv
Component: CalcAssignee: Not Assigned <libreoffice-bugs>
Status: RESOLVED INVALID    
Severity: normal CC: barta, lo_bugs
Priority: medium    
Version: 4.2.4.1 rc   
Hardware: x86-64 (AMD64)   
OS: macOS (All)   
Whiteboard:
Crash report or crash signature: Regression By:
Attachments: crash log

Description printcsv 2014-04-15 21:00:58 UTC
Created attachment 97427 [details]
crash log

LibreOffice/OSX crashes when trying to open a .xlsm spreadsheet file with many macros. The file has been created in Excel, edited in LibreOffice several times, the crashing instance is written by LibreOffice. The crash seems to happen in string processing routines. (dump attached).
Comment 1 Terrence Enger 2014-04-15 21:39:19 UTC
@printcsv,

Can you attach the file which provokes the crash?  Keep in mind that bug attachments are visible to the whole world.

Failing that, can you share the file wit interested individuals?  Or, can you wipe out confidential information so that the resulting file stil makes LibreOffice crash?

When you respond, with the attachment or otherwise, please set the bug status back to UNCONFIRMED.

The crash log identifies LibreOffice as version 4.2.4 (0), so I am setting the version field of the report to 4.2.1 rc, as this seems to be the closest version offered.  This field reporesents the earliest version of LibreOffice in which the bug has been sighted; expect it to change if anybody can reproduce the bug with an earlier version.

Thanks,
Terry.
Comment 2 printcsv 2014-04-16 09:18:19 UTC
Unfortunately I cannot share this file, since it is impossible to edit it until the crash bug is fixed, and therefore I cannot replace sensitive information. Is there anything I can do to help debugging or narrowing down the issue?
Comment 3 Terrence Enger 2014-04-16 14:58:04 UTC
A couple of ideas, none of them very easy, I fear:

(1) Use another program, perhaps Excel, to strip the confidential
    information from your file.

(2) If the present bug happens to be a regression, and if you have
    enough bandwidth and disk storage, an older version of LibreOffice
    available through "How to Bibisect"
    <https://wiki.documentfoundation.org/QA/HowToBibisect> may let you
    open the file so that you can remove confidential information.  As
    a happy byproduct, the process will identify approximately when
    the bug entered LibreOffice.  I do not use Mac, so you will need
    to find help elsewhere if you have problems.

(3) Install valgrind, run LibreOffice with command-line option
    --valgrind and make the crash, and attach a typescript of the
    terminal output.
Comment 4 tommy27 2014-04-30 23:17:30 UTC
let's put this in NEEDINFO state until a test case is available.
without it il will be impossible to reproduce the issue.
Comment 5 QA Administrators 2014-11-02 16:46:45 UTC
Dear Bug Submitter,

This bug has been in NEEDINFO status with no change for at least 6 months. Please provide the requested information as soon as possible and mark the bug as UNCONFIRMED. Due to regular bug tracker maintenance, if the bug is still in NEEDINFO status with no change in 30 days the QA team will close the bug as INVALID due to lack of needed information.

For more information about our NEEDINFO policy please read the wiki located here: 
https://wiki.documentfoundation.org/QA/FDO/NEEDINFO

If you have already provided the requested information, please mark the bug as UNCONFIRMED so that the QA team knows that the bug is ready to be confirmed.


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


Warm Regards,
QA Team
Comment 6 QA Administrators 2015-01-02 17:13:36 UTC
Dear Bug Submitter,

Please read this message in its entirety before proceeding.

Your bug report is being closed as INVALID 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 FDO