Bug 719191 - [abrt] libreoffice-writer- __GI_raise: Process /usr/lib64/libreoffice/program/swriter.bin was killed by signal 6 (SIGABRT)
[abrt] libreoffice-writer- __GI_raise: Process /usr/lib64/libr...
Product: Fedora
Classification: Fedora
Component: java-1.6.0-openjdk (Show other bugs)
x86_64 Unspecified
unspecified Severity unspecified
: ---
: ---
Assigned To: Deepak Bhole
Fedora Extras Quality Assurance
Depends On:
  Show dependency treegraph
Reported: 2011-07-05 21:43 EDT by Scott Williams
Modified: 2012-08-07 11:56 EDT (History)
14 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2012-08-07 11:56:25 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)
File: dso_list (21.13 KB, text/plain)
2011-07-05 21:44 EDT, Scott Williams
no flags Details
File: maps (86.67 KB, text/plain)
2011-07-05 21:44 EDT, Scott Williams
no flags Details
File: backtrace (119.77 KB, text/plain)
2011-07-05 21:44 EDT, Scott Williams
no flags Details

  None (edit)
Description Scott Williams 2011-07-05 21:43:59 EDT
abrt version: 2.0.3
architecture:   x86_64
backtrace_rating: 4
cmdline:        /usr/lib64/libreoffice/program/swriter.bin -writer '/home/scott/Desktop/scott/Documents/School/ANE History/Mesopotamia.odt'
comment:        Program crashed immediately upon opening an .odt document.
component:      libreoffice
crash_function: __GI_raise
executable:     /usr/lib64/libreoffice/program/swriter.bin
os_release:     Fedora release 15 (Lovelock)
package:        libreoffice-writer-
reason:         Process /usr/lib64/libreoffice/program/swriter.bin was killed by signal 6 (SIGABRT)
time:           Tue Jul  5 18:13:46 2011
uid:            500
username:       scott

backtrace:      Text file, 122643 bytes
dso_list:       Text file, 21637 bytes
maps:           Text file, 88749 bytes

:'LESSOPEN=||/usr/bin/lesspipe.sh %s'
Comment 1 Scott Williams 2011-07-05 21:44:02 EDT
Created attachment 511415 [details]
File: dso_list
Comment 2 Scott Williams 2011-07-05 21:44:03 EDT
Created attachment 511416 [details]
File: maps
Comment 3 Scott Williams 2011-07-05 21:44:05 EDT
Created attachment 511417 [details]
File: backtrace
Comment 4 David Tardon 2011-07-06 01:01:36 EDT
the crashing thread is java garbage collector -> not ours
Comment 5 Deepak Bhole 2011-07-06 09:59:07 EDT
This does look like a GC issue. Scott, is it reproducible?
Comment 6 abrt-bot 2012-03-30 09:28:34 EDT
*** Bug 731614 has been marked as a duplicate of this bug. ***
Comment 7 abrt-bot 2012-03-30 09:28:50 EDT
*** Bug 702507 has been marked as a duplicate of this bug. ***
Comment 8 Michael Stahl 2012-04-02 06:05:21 EDT
abrt-bot is wrong:
Bug 731614 and Bug 702507 are not duplicates.
the 10 or so signal handler frames that the JVM always puts
on the stack apparently confuse abrt-bot and make let it erroneously
detect these as duplicate.
Comment 9 Fedora End Of Life 2012-08-07 11:56:31 EDT
This message is a notice that Fedora 15 is now at end of life. Fedora
has stopped maintaining and issuing updates for Fedora 15. It is
Fedora's policy to close all bug reports from releases that are no
longer maintained. At this time, all open bugs with a Fedora 'version'
of '15' have been closed as WONTFIX.

(Please note: Our normal process is to give advanced warning of this
occurring, but we forgot to do that. A thousand apologies.)

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

Bug Reporter: Thank you for reporting this issue and we are sorry that
we were unable to fix it before Fedora 15 reached 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 to click on
"Clone This Bug" (top right of this page) and open it against that
version of Fedora.

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.

The process we are following is described here:

Note You need to log in before you can comment on or make changes to this bug.