Issue 126795 - intermittent crash when opening .ods
Summary: intermittent crash when opening .ods
Status: UNCONFIRMED
Alias: None
Product: Calc
Classification: Application
Component: open-import (show other issues)
Version: 4.1.2
Hardware: Mac OS X 10.11
: P5 (lowest) Normal (vote)
Target Milestone: ---
Assignee: AOO issues mailing list
QA Contact:
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2016-01-17 22:19 UTC by Chris Withers
Modified: 2017-05-20 11:55 UTC (History)
3 users (show)

See Also:
Issue Type: DEFECT
Latest Confirmation in: ---
Developer Difficulty: ---

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this issue.
Description Chris Withers 2016-01-17 22:19:41 UTC 
I'm pretty sure this started after upgrading to El Capitan, but now I get intermittent crashes when opening .ods files.

This takes out the whole app such that other spreadsheets open lose recent changes. While the recovery on restart says it's successful, all changes since other open files were last saved are lost.
Comment 1 oooforum (fr) 2016-01-18 10:14:29 UTC 
Don't open multiple issues for a same problem

*** This issue has been marked as a duplicate of issue 126796 ***
Comment 2 Chris Withers 2016-01-18 10:29:36 UTC 
I don't think this is a dupe.

This issue was for a crash on opening a .ods, the other was for an infinite loop while using the UI.

What can I do to get OOo to spit out logs when it crashes-on-opening?

Can I get OS X to spit out a core file for you guys?
Comment 3 oooforum (fr) 2016-01-18 10:53:01 UTC 
So provide a sample document to reproduce.
Comment 4 Chris Withers 2016-01-18 11:08:52 UTC 
@oooforum - your attitude comes across as overly aggressive, is it really necessary?

I opened this issue to track it as an intermittent failure.

As an open source developer, I know these are the hardest kind of issues to debug, made more so as the file I was working with contains confidential data that I can't share on a public issue tracker.

As soon as I encounter a file I can add to a public tracker and which reliably demonstrates the issue, I will of course add it.

In the meantime, if you or anyone else could answer my questions, that would be great:

What can I do to get OOo to spit out logs when it crashes-on-opening?
(if it already does, please let me know where I can look)

Can I get OS X to spit out a core file to aid debugging?
Comment 5 oooforum (fr) 2016-04-21 10:26:18 UTC 
No news from OP since +3 months

Feel free to reopen with required information:
Of course, a sample document with anonymous content.
Comment 6 cjw296 2016-04-21 10:39:33 UTC 
@oooforum - huh? I replied and asked two questions:

What can I do to get OOo to spit out logs when it crashes-on-opening?
(if it already does, please let me know where I can look)

Can I get OS X to spit out a core file to aid debugging?

I never got a response...
Comment 7 cjw296 2016-04-21 10:40:45 UTC 
So, how do I re-open?
Comment 8 orcmid 2016-04-21 14:30:21 UTC 
(In reply to cjw296 from comment #7)
> So, how do I re-open?

The issue remains and you can continue to add information, especially helping to create a reproducible case.

I suggest you re-ask your questions on dev@openoffice.apache.org where there might be more developer attention.  Identify this issue (126795) too.