Bug 832603
Summary: | [abrt] libreoffice-core-3.5.4.2-1.fc17: FocusManager::RemoveUnusedEventListener killed by signal 11 (SIGSEGV) | ||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | saulo <sauloal> | ||||||||||
Component: | libreoffice | Assignee: | Caolan McNamara <caolanm> | ||||||||||
Status: | CLOSED ERRATA | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||||||||
Severity: | unspecified | Docs Contact: | |||||||||||
Priority: | unspecified | ||||||||||||
Version: | 17 | CC: | caolanm, dtardon, erack, ltinkl, mstahl, sbergman, sir.ade, stedchris | ||||||||||
Target Milestone: | --- | ||||||||||||
Target Release: | --- | ||||||||||||
Hardware: | x86_64 | ||||||||||||
OS: | Unspecified | ||||||||||||
Whiteboard: | abrt_hash:36242fe841d8a0d61168f0f78e178d3e3138021f | ||||||||||||
Fixed In Version: | libreoffice-3.5.5.3-5.fc17 | Doc Type: | Bug Fix | ||||||||||
Doc Text: | Story Points: | --- | |||||||||||
Clone Of: | Environment: | ||||||||||||
Last Closed: | 2012-08-19 00:27:22 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
saulo
2012-06-15 22:06:16 UTC
Created attachment 592247 [details]
File: dso_list
Created attachment 592248 [details]
File: maps
Created attachment 592249 [details]
File: backtrace
Created attachment 592250 [details]
File: core_backtrace
Are you able to reproduce this crash ? If so how ? I wonder if this is somehow related to http://cgit.freedesktop.org/libreoffice/core/commit/?id=ec240ea + http://cgit.freedesktop.org/libreoffice/core/commit/?id=4ae4c57 Clearly some lifecycle disaster on deleting a Window *** Bug 835481 has been marked as a duplicate of this bug. *** *** Bug 844156 has been marked as a duplicate of this bug. *** Lets turn off c++0x mode in F-17 in case that's the problem here (In reply to comment #8) > Lets turn off c++0x mode in F-17 in case that's the problem here I do not believe that that's the problem here. For one, accidentally picking up wrong implementations of inline functions across libraries (see <http://gcc.gnu.org/bugzilla/show_bug.cgi?id=49561#c8> "[C++0x] std::list::size complexity") cannot hit here, as the relevant code is built --fvisibility-inlines-hidden (and libvcllo.so indeed contains "std::__debug::list<Link, std::allocator<Link> >::remove(Link const&)" only non-exported). For another, the backtrace in attachment 601026 [details] to bug 844156, where the relevant std::list instance's this=0x4f, makes it more likely that this is indeed some lifecycle disaster/memory corruption. (Then again, turning c++0x mode off in F-17 probably cannot hurt anyway, at least as long as <http://gcc.gnu.org/bugzilla/show_bug.cgi?id=49561> is only fixed in rawhide.) https://bugs.freedesktop.org/show_bug.cgi?id=47368 looks like a possible culprit libreoffice-3.5.5.3-5.fc17 has been submitted as an update for Fedora 17. https://admin.fedoraproject.org/updates/libreoffice-3.5.5.3-5.fc17 https://bugs.freedesktop.org/show_bug.cgi?id=51324#c25 It seems that gcc -std=c++11 is innocent after all. Package libreoffice-3.5.5.3-5.fc17: * should fix your issue, * was pushed to the Fedora 17 testing repository, * should be available at your local mirror within two days. Update it with: # su -c 'yum update --enablerepo=updates-testing libreoffice-3.5.5.3-5.fc17' as soon as you are able to. Please go to the following url: https://admin.fedoraproject.org/updates/FEDORA-2012-11418/libreoffice-3.5.5.3-5.fc17 then log in and leave karma (feedback). libreoffice-3.5.6.2-1.fc17 has been submitted as an update for Fedora 17. https://admin.fedoraproject.org/updates/libreoffice-3.5.6.2-1.fc17 libreoffice-3.5.6.2-1.fc17 has been pushed to the Fedora 17 stable repository. If problems still persist, please make note of it in this bug report. |