Bug 114064 - LibreOffice Writer crashing for no apparent reason
Summary: LibreOffice Writer crashing for no apparent reason
Status: RESOLVED INSUFFICIENTDATA
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Writer (show other bugs)
Version:
(earliest affected)
5.2.6.2 release
Hardware: x86-64 (AMD64) macOS (All)
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
: 112022 (view as bug list)
Depends on:
Blocks:
 
Reported: 2017-11-26 15:34 UTC by Sam
Modified: 2018-09-03 14:57 UTC (History)
1 user (show)

See Also:
Crash report or crash signature:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Sam 2017-11-26 15:34:11 UTC
[This replaces Bug 112022 – all the relevant info from there is found in this description.]

LibreOffice Writer keeps crashing for no apparent reason. While everything seems to be fine when working on a file, suddenly, out of the blue, LibreOffice Writer crashes after I was doing any of the following: (a) typing some text, (b) navigating the document, (c) changing a setting, or (d) moving the mouse over the screen. Whether any of this happens is entirely unpredictable – it may occur from anything within a few seconds to a few hours working on a file. It may have been an .odt, .doc, .docx, or .rtf file. The file may be any fresh one (when it is still almost empty) or an existing one, in other words, the problem does not seem to be file-related.

For example, once I opened a fresh file, and the *only* thing I did was go to View and choose Web – and then it crashed. (Document Recovery worked fine, but there was no error report to submit.) Opening a fresh file again and doing the same thing worked afterwards. So the crashing is unpredictable.

The crash happens with the following fresh or still LO versions:
5.2.6.2
5.3.5.2.
5.4 Dev.

When a crash occurs there may be (1) no message at all, (2) a Problem Report, (3) the message "Due to an unexpected error, LibreOffice crashed. All the files you were working on will now be saved. The next time LibreOffice is launched, your files will be recovered automatically. The following files will be recovered: ...", or (4) the message "Either another instance of LibreOfficeDev is accessing your personal settings or your personal settings are locked. Simultaneous access can lead to inconsistencies in your personal settings. Before continuing, you should make sure user '<username>' closes LibreOfficeDev on host '<hostname>'. – Do you really want to continue?"

This problem only began to occur with my new MacBook Pro Early 2015 I bought a year ago (on my older Mac, with Mountain Lion, I never had this problem with LO). I'm running macOS Sierra 10.12.6 now, and all other applications work fine – the crashing is limited to LibreOffice. At the Apple Shop they won't offer me support because LO is not an Apple product (they suggested I use MS Office instead).

So far I have tried using the LO Dev version to obtain meaningful crash reports, and I've installed Xcode command line tools. However, I'm no superuser so I am only able to follow step-by-step advice.

JDK:
Java(TM) SE Runtime Environment (build 1.8.0_144-b01)
Java HotSpot(TM) 64-Bit Server VM (build 25.144-b01, mixed mode)

I'm not using Nuance Dragon Dictate.

On the positive side, Document Recovery works fine always, and I don't seem to have lost any data so far (and LO Writer is otherwise great for me). Still, all this is really annoying.
Comment 1 Dieter 2017-11-26 16:31:03 UTC
*** Bug 112022 has been marked as a duplicate of this bug. ***
Comment 2 Alex Thurgood 2017-11-27 10:33:40 UTC
@Sam : as Telesto pointed out in comment 41 of bug 112022, it would seem that the problem lies with a particular document. If that is the case, then we would need a sample document where the behaviour is reproducible.

As such, I see little point in opening a new bug report if all we can see is the same as your initial report in bug 112022.

Currently, this present report is just as vague and unreproducible as your first report. To that extent, this present report is merely a DUPLICATE of the previous one. Until you can be more specific and provide reproducible conditions under which the crash occurs, there is little else we can do.
Comment 3 Xisco Faulí 2018-01-24 09:42:40 UTC
(In reply to Alex Thurgood from comment #2)
> @Sam : as Telesto pointed out in comment 41 of bug 112022, it would seem
> that the problem lies with a particular document. If that is the case, then
> we would need a sample document where the behaviour is reproducible.

I have set the bug's status to 'NEEDINFO'. Please change it back to 'UNCONFIRMED' once the requested document is provided.
Comment 4 QA Administrators 2018-07-31 09:38:12 UTC Comment hidden (obsolete)
Comment 5 QA Administrators 2018-09-03 14:57:25 UTC
Dear Bug Submitter,

Please read this message in its entirety before proceeding.

Your bug report is being closed as INSUFFICIENTDATA 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 our bug tracker

Warm Regards,
QA Team

MassPing-NeedInfo-20180903