Bug 947095

Created attachment 730313 [details]
File: backtrace

Created attachment 730314 [details]
File: build_ids

Created attachment 730315 [details]
File: cgroup

Created attachment 730316 [details]
File: core_backtrace

Created attachment 730317 [details]
File: dso_list

Created attachment 730318 [details]
File: environ

Created attachment 730319 [details]
File: limits

Created attachment 730320 [details]
File: maps

Created attachment 730321 [details]
File: open_fds

Created attachment 730322 [details]
File: proc_pid_status

Created attachment 730323 [details]
File: smolt_data

Created attachment 730324 [details]
File: var_log_messages

"Looks like gdb hung while generating backtrace.", bah, so we don't have enough information here in the auto report. Are you able to reproduce the crash manually ?

It appears I can reproduce, though not exactly at will. It seems to happen when I have a large presentation open (~65 slides), and scroll around, jump back and forth between Normal and Arrange Slides, etc. Couldn't pin down exactly what it was. I don't think it's ever crashed when I didn't also have Calc running simultaneously, not that I've really tried.

abrt again gave me the message "Timeout exceeded: 240 seconds, killing gdb.
Looks like gdb hung while generating backtrace." Is there another way I can assist with debugging?

I just realized it doesn't explicitly say in this bug... it's Impress that is crashing. Haven't had a problem with Calc on its own.

it might help to run directly under gdb, i.e.

gdb /usr/lib64/libreoffice/program/soffice.bin
(gdb) run

and get it to crash, and at that point
(gdb) bt
and paste in the backtrace

Attaching a new backtrace. I installed the package libreoffice-gdb-debug-support, not sure if that was necessary. I considered running "debuginfo-install libreoffice-core-3.6.5.2-8.fc18.x86_64" but that wanted to install 3.9G of dependencies, so I skipped it. Let me know if I should do that and try again, or if there's anything else I can do.

It seems I can reproduce the crash most of the time by clicking on the "Outline" tab, and then back to "Normal", but that's not the only way it has happened.

Created attachment 731984 [details]
gdb output

don't see it in a trivial presentation, perhaps the presentation size is a factor in reproducing this. If you can attach your presentation, that might help

no warnings from valgrind on an empty presentation on switching from outline to normal repeatedly

Sorry, I can't share the original presentation.

However, I'm able to cause it to crash simply by creating a new presentation, inserting a table, and switching to Outline view. I did this several times this morning; the gdb backtrace looks a bit different than the previous one, so attaching a couple of those.

Created attachment 732792 [details]
another gdb backtrace

Created attachment 732793 [details]
yet another gdb backtrace

I suppose the crash is related to the right panel (which is hidden in the outline view), but I am not getting any crash. valgrind only shows

==9496== Invalid read of size 8
==9496==    at 0x8FB9A9F: Application::GetSolarMutex() (svapp.cxx:479)
==9496==    by 0x23D2D020: SolarMutexGuard::SolarMutexGuard() (svapp.hxx:403)
==9496==    by 0x23D392C2: accessibility::AccessibleTextHelper_Impl::~AccessibleTextHelper_Impl() (AccessibleTextHelper.cxx:287)
...

on quit, which is worth to check, but probably unrelated.

This message is a reminder that Fedora 18 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 18. 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 WONTFIX if it remains open with a Fedora 
'version' of '18'.

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 prior to Fedora 18's end of life.

Thank you for reporting this issue and we are sorry that we may not be 
able to fix it before Fedora 18 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 to Fedora 18's end of life.

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 18 changed to end-of-life (EOL) status on 2014-01-14. Fedora 18 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.