Bug 72649 - Unexpected crash
Summary: Unexpected crash
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Writer (show other bugs)
(earliest affected) release
Hardware: Other Linux (All)
: medium normal
Assignee: Not Assigned
Whiteboard: BSA
Keywords: haveBacktrace
Depends on:
Reported: 2013-12-12 20:45 UTC by Nicholas Jackson
Modified: 2014-08-04 16:15 UTC (History)
4 users (show)

See Also:
Crash report or crash signature:

gdb trace (13.63 KB, text/x-log)
2013-12-12 20:45 UTC, Nicholas Jackson
gdb trace 2 (34.94 KB, text/x-log)
2013-12-15 12:13 UTC, Nicholas Jackson

Note You need to log in before you can comment on or make changes to this bug.
Description Nicholas Jackson 2013-12-12 20:45:46 UTC
Created attachment 90677 [details]
gdb trace

Problem description: LibreOffice Writer crashes randomly and unexpectedly.

Steps to reproduce: I'm afraid I can't provide any useful information on how to reproduce the crash, in what circumstances it happens, or what the likely cause might be. I've attached a gdb trace file, but other than that I have no further useful information. Sorry.

Current behavior: Unexpected crash while editing medium length Word document.

Expected behavior: Not crashing.     
Operating System: Ubuntu
Version: release
Comment 1 Julien Nabet 2013-12-12 21:07:15 UTC
I made a search on Opengrok and found this:

Then looking at the history, I saw this:

Michael: of course it's just guessing since we don't have steps to reproduce the problem and perhaps I'm far too optimistic here but could this commit above could help here?
Comment 2 Nicholas Jackson 2013-12-15 12:13:16 UTC
Created attachment 90799 [details]
gdb trace 2

Here's another gdb trace. I'm afraid I've no idea whether this is related or not, but maybe it'll be useful to someone.
Comment 3 tommy27 2013-12-28 14:17:19 UTC
r u still seeing crashes in
Comment 4 retired 2013-12-31 10:28:55 UTC
Setting to NEEDINFO until more detail is provided as of comment 3.

After providing the requested info, please reset this bug to UNCONFIRMED. Thanks :)
Comment 5 Nicholas Jackson 2013-12-31 11:38:28 UTC
I'm sorry, I don't have any more information at the moment. I'll try to find time to install and see if that's any more stable.
Comment 6 Julien Nabet 2013-12-31 11:56:04 UTC
So let's this bugtracker back to NEEDINFO for the moment, waiting for your feedback.
Comment 7 QA Administrators 2014-07-08 17:29:09 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: 

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 8 QA Administrators 2014-08-04 16:15:12 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