Bug 711882 - [abrt] openoffice.org-brand-1:3.3.0-20.5.fc14: Process /usr/lib64/openoffice.org3/program/soffice.bin was killed by signal 6 (SIGABRT)
Summary: [abrt] openoffice.org-brand-1:3.3.0-20.5.fc14: Process /usr/lib64/openoffice....
Keywords:
Status: CLOSED INSUFFICIENT_DATA
Alias: None
Product: Fedora
Classification: Fedora
Component: openoffice.org
Version: 14
Hardware: x86_64
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Caolan McNamara
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:91d1c20009d18d19aa465fba0fa...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-06-08 20:52 UTC by Steve Kelem
Modified: 2011-06-17 15:03 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2011-06-17 15:03:09 UTC
Type: ---


Attachments (Terms of Use)
File: backtrace (77.06 KB, text/plain)
2011-06-08 20:52 UTC, Steve Kelem
no flags Details

Description Steve Kelem 2011-06-08 20:52:00 UTC
abrt version: 1.1.18
architecture: x86_64
Attached file: backtrace, 78905 bytes
cmdline: /usr/lib64/openoffice.org3/program/soffice-3.3.bin
comment: I deleted a number of sections in my document, with Record Changes turned on, and Show Changes turned off.
component: openoffice.org
Attached file: coredump, 323354624 bytes
crash_function: __cxxabiv1::__terminate(void (*)())
executable: /usr/lib64/openoffice.org3/program/soffice.bin
kernel: 2.6.35.13-91.fc14.x86_64
package: openoffice.org-brand-1:3.3.0-20.5.fc14
rating: 4
reason: Process /usr/lib64/openoffice.org3/program/soffice.bin was killed by signal 6 (SIGABRT)
release: Fedora release 14 (Laughlin)
time: 1307565964
uid: 1010

How to reproduce
-----
1. OO got into an infinite loop, consuming all the cpu cycles and swap space
2.
3.

Comment 1 Steve Kelem 2011-06-08 20:52:01 UTC
Created attachment 503782 [details]
File: backtrace

Comment 2 David Tardon 2011-06-09 06:44:41 UTC
How did you remove the sections? Using the Remove button in Format->Sections? Or otherwise? Can you reproduce it?


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