Bug 828516
Summary: | [abrt] libreoffice-core-3.5.3.2-3.fc17: _XIOError -> FontSubstConfiguration dtor: killed by signal 11 (SIGSEGV) | ||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Matthieu Pupat <redhat_bugzilla> | ||||||||
Component: | libreoffice | Assignee: | Caolan McNamara <caolanm> | ||||||||
Status: | CLOSED WONTFIX | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||||||
Severity: | unspecified | Docs Contact: | |||||||||
Priority: | unspecified | ||||||||||
Version: | 17 | CC: | caolanm, dtardon, erack, ltinkl, mstahl, sbergman | ||||||||
Target Milestone: | --- | ||||||||||
Target Release: | --- | ||||||||||
Hardware: | x86_64 | ||||||||||
OS: | Unspecified | ||||||||||
Whiteboard: | abrt_hash:b17c2195a61788e67b9c2a52c74fb1a29ffe089c | ||||||||||
Fixed In Version: | Doc Type: | Bug Fix | |||||||||
Doc Text: | Story Points: | --- | |||||||||
Clone Of: | Environment: | ||||||||||
Last Closed: | 2012-06-05 11:06:54 UTC | Type: | --- | ||||||||
Regression: | --- | Mount Type: | --- | ||||||||
Documentation: | --- | CRM: | |||||||||
Verified Versions: | Category: | --- | |||||||||
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||||||
Cloudforms Team: | --- | Target Upstream Version: | |||||||||
Embargoed: | |||||||||||
Attachments: |
|
Description
Matthieu Pupat
2012-06-04 20:13:53 UTC
Created attachment 589272 [details]
File: build_ids
Created attachment 589273 [details]
File: maps
Created attachment 589274 [details]
File: backtrace
An unexpected XIOError leading to FontSubstConfiguration shutdown and a crash during that. Odd thing is that the dtors seem to be called from thread 3 and not thread 1 as I'd expect. Don't really know what that is. Anyway, we can't survive an XIOError (x server connection gone away) so while it'd be nicer to have a cleaner shutdown on disconnect its not a serious problem in the absence of an easy-fix. (In reply to comment #4) > Odd thing is that the dtors seem to be called from thread > 3 and not thread 1 as I'd expect. Don't really know what that is. Looks like both the main thread (reported as thread #3) and the SelectionManager thread (reported as thread #1) raced for _XIOError -> ... -> __run_exit_handlers, and the main thread happened to win. |