Bug 691083 - [abrt] openoffice.org-brand-1:3.3.0-20.2.fc14: X11GlyphCache::GetInstance: Process /usr/lib/openoffice.org3/program/soffice.bin was killed by signal 11 (SIGSEGV)
Summary: [abrt] openoffice.org-brand-1:3.3.0-20.2.fc14: X11GlyphCache::GetInstance: Pr...
Keywords:
Status: CLOSED INSUFFICIENT_DATA
Alias: None
Product: Fedora
Classification: Fedora
Component: openoffice.org
Version: 14
Hardware: i686
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Caolan McNamara
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:1ce3d330c0b45f9daedf83aa5a9...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-03-26 16:16 UTC by dani882
Modified: 2011-04-18 13:54 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2011-04-18 13:54:07 UTC
Type: ---


Attachments (Terms of Use)
File: backtrace (27.88 KB, text/plain)
2011-03-26 16:16 UTC, dani882
no flags Details

Description dani882 2011-03-26 16:16:23 UTC
abrt version: 1.1.17
architecture: i686
Attached file: backtrace, 28546 bytes
cmdline: /usr/lib/openoffice.org3/program/soffice.bin -quickstart -nologo -nodefault
component: openoffice.org
Attached file: coredump, 48164864 bytes
crash_function: X11GlyphCache::GetInstance
executable: /usr/lib/openoffice.org3/program/soffice.bin
kernel: 2.6.35.11-83.fc14.i686
package: openoffice.org-brand-1:3.3.0-20.2.fc14
rating: 4
reason: Process /usr/lib/openoffice.org3/program/soffice.bin was killed by signal 11 (SIGSEGV)
release: Fedora release 14 (Laughlin)
time: 1301122377
uid: 500

How to reproduce
-----
1.anything
2.
3.

Comment 1 dani882 2011-03-26 16:16:26 UTC
Created attachment 487860 [details]
File: backtrace

Comment 2 Caolan McNamara 2011-03-28 08:36:20 UTC
I don't see any immediate reason why this would happen. Looks like the very first font request. Clearly this doesn't happen for me and for most people, so...
"how to reproduce: anything", does that mean it always happens for you ?, or just once ?

Comment 3 Caolan McNamara 2011-04-17 22:18:09 UTC
Can't reproduce this, there's no evidence that there are multiple threads going on in this area, but I don't like the look of X11GlyphCache::GetInstance with a multi-thread head on

Comment 4 Caolan McNamara 2011-04-18 13:54:07 UTC
upstream I've made sure this is threadsafe. I'm unconvinced that this is exactly the problem we have here, which I'm unable to reproduce. 

(http://cgit.freedesktop.org/libreoffice/libs-gui/commit/?id=2acdffcaa1f529955ac57bd773c906eb26fb9582)


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