Bug 671350 - [abrt] openoffice.org-calc-1:3.3.0-19.2.fc14: rtl_cache_slab_alloc: Process /usr/lib64/openoffice.org3/program/scalc.bin was killed by signal 11 (SIGSEGV)
Summary: [abrt] openoffice.org-calc-1:3.3.0-19.2.fc14: rtl_cache_slab_alloc: Process /...
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:b2f6b859f00a23852807d4621a1...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-01-21 10:40 UTC by tomas
Modified: 2011-01-26 16:14 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2011-01-26 16:14:37 UTC
Type: ---


Attachments (Terms of Use)
File: backtrace (76.79 KB, text/plain)
2011-01-21 10:40 UTC, tomas
no flags Details

Description tomas 2011-01-21 10:40:32 UTC
abrt version: 1.1.14
architecture: x86_64
Attached file: backtrace
cmdline: /usr/lib64/openoffice.org3/program/scalc.bin -calc
component: openoffice.org
crash_function: rtl_cache_slab_alloc
executable: /usr/lib64/openoffice.org3/program/scalc.bin
kernel: 2.6.35.10-74.fc14.x86_64
package: openoffice.org-calc-1:3.3.0-19.2.fc14
rating: 4
reason: Process /usr/lib64/openoffice.org3/program/scalc.bin was killed by signal 11 (SIGSEGV)
release: Fedora release 14 (Laughlin)
time: 1295602893
uid: 500

How to reproduce
-----
1.in the time of construction a pivot-table
2.
3.

Comment 1 tomas 2011-01-21 10:40:41 UTC
Created attachment 474610 [details]
File: backtrace

Comment 2 Caolan McNamara 2011-01-21 15:35:58 UTC
Much of the backtrace is sort of missing for some reason. Are you able to reproduce this ?

Comment 3 tomas 2011-01-21 15:57:20 UTC
I'am sorry, I mean, that it was happend if I construct a pivot-table, which had a cell in the first line empty. After the crash, I open calc, restore program and work without new problems.

Comment 4 Caolan McNamara 2011-01-26 12:19:59 UTC
I imagine something takes soo long that the autosave kicks in or something and the whole affair gets confused and falls over with a massive alloc.

Are you able to get it to happen again. I'd need an exact step-by-step, ideally e.g. a sample document ?

Comment 5 tomas 2011-01-26 14:31:12 UTC
I am not able to reproduce this crash. I have a few problems with open office, but it was the problem, registrated by system for automatic registration. And I don't know, how to reproduce it. Normaly there are problems with pivot table, but without the programcrash.

Comment 6 Caolan McNamara 2011-01-26 16:14:37 UTC
A pity, I suspect either out of memory or some horrible timing issue about autosaves during long operations.


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