Bug 1089077

Created attachment 887296 [details]
File: backtrace

Created attachment 887297 [details]
File: cgroup

Created attachment 887298 [details]
File: core_backtrace

Created attachment 887299 [details]
File: dso_list

Created attachment 887300 [details]
File: environ

Created attachment 887301 [details]
File: exploitable

Created attachment 887302 [details]
File: limits

Created attachment 887303 [details]
File: maps

Created attachment 887304 [details]
File: open_fds

Created attachment 887305 [details]
File: proc_pid_status

Created attachment 887306 [details]
File: var_log_messages

Another user experienced a similar problem:

Changed line spacing of a large document and scrolled a little too quickly.

reporter:       libreport-2.2.2
backtrace_rating: 3
cmdline:        /usr/lib64/libreoffice/program/soffice.bin --impress file:///home/milan/EHESS/Homogamie/LFS/Budapest/Poster%20Budapest.odp --splash-pipe=5
crash_function: get_previous_start
executable:     /usr/lib64/libreoffice/program/soffice.bin
kernel:         3.13.10-200.fc20.x86_64
package:        libreoffice-core-4.2.3.3-9.fc20
reason:         soffice.bin killed by SIGSEGV
runlevel:       N 5
type:           CCpp
uid:            1000

a font cache problem I suspect

Yeah, this is again using Linux Libertine G in a long Writer document. I've not been able to reproduce the crash again with a few attempts. Note that I had opened several similar documents, modified them, and closed most of them. So there may be something with incorrectly freed memory.

Another user experienced a similar problem:

Crashed while drag-and-dropping an element on a master slide (Impress).

reporter:       libreport-2.2.3
backtrace_rating: 3
cmdline:        /usr/lib64/libreoffice/program/soffice.bin --impress '/tmp/intoPIX - TICO Technical Presentation - 2014 06 15 - IPX_GRO.pptx' --splash-pipe=5
crash_function: get_previous_start
executable:     /usr/lib64/libreoffice/program/soffice.bin
kernel:         3.15.6-200.fc20.x86_64
package:        libreoffice-core-4.2.5.2-10.fc20
reason:         soffice.bin killed by SIGSEGV
runlevel:       N 5
type:           CCpp
uid:            1000

Another user experienced a similar problem:

Crashed when scrolling too fast in a Writer doc.

reporter:       libreport-2.2.3
backtrace_rating: 3
cmdline:        /usr/lib64/libreoffice/program/soffice.bin --impress file:///home/milan/EHESS/Homogamie/INED/Journ%C3%A9e%20GRAB%20SFdS/Journ%C3%A9e%20GRAB%20SFdS.odp --splash-pipe=5
crash_function: get_previous_start
executable:     /usr/lib64/libreoffice/program/soffice.bin
kernel:         3.16.3-200.fc20.x86_64
package:        libreoffice-core-4.2.6.3-8.fc20
reason:         soffice.bin killed by SIGSEGV
runlevel:       N 5
type:           CCpp
uid:            1000

Have we a reproducible scenario ? i.e. a document I could open and reproduce the problem with.

Caolan: I've just sent to you the document with which I've experienced the crash several times. This document is generated by R/odfWeave based on an ODF containing code. This means I very often reload the document, and scroll quite fast while it's loading images. I cannot be sure that's the problem, but it seems the crash happens when scrolling too fast while the layout is being updated. But then what would be the relationship with the fonts cache, no idea...

Another possible explanation is that running R consumes quite a bit of memory, which triggers delays when reloading the document. Maybe there's a race condition between scrolling and updating the view, which is too hard to trigger under normal RAM conditions.

*grumble*, why am I never able to reproduce these things.

(In reply to Caolan McNamara from comment #19)
> *grumble*, why am I never able to reproduce these things.

Maybe because your machine is fast and the bug only happens when the system is slowed down by memory pressure? I think we discussed this already. Maybe you could try filling your memory to reproduce these conditions...

Nothing under valgrind either. But now that I think about it I was using an self-build upstream mode 4.2 and not the stock Fedora one which uses system graphite which might make a difference. Will try again.

and nothing for me with 4.2 LibreOffice. Maybe I didn't get the right "G" fonts installed. Can I get the output of fc-list -v ?

(if you want to try and get a valgrind trace yourself its...

export VALGRIND=memcheck
oowriter file.odt > ~/valgrind.log 2>&1
and attach the valgrind.log if office crashes or there is anything suspicious in the log.

Actually I've not been able to reproduce the problem now after quite a few attempts. I seems to only happen when I want to concentrate on my work! Unfortunately, running inside Valgrind is so slow that I really can't work with it waiting for the bug to happen again. Any other debugging solution available? Maybe adding a few lines of code would be enough to print interesting information before the crash happens?

*** Bug 1127567 has been marked as a duplicate of this bug. ***

This message is a reminder that Fedora 20 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 20. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as EOL if it remains open with a Fedora  'version'
of '20'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora 20 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora, you are encouraged  change the 'version' to a later Fedora 
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

Fedora 20 changed to end-of-life (EOL) status on 2015-06-23. Fedora 20 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.