| Summary: | [abrt] libreoffice-core-3.4.5.2-8.fc16: OUString: Process /usr/lib64/libreoffice/program/soffice.bin was killed by signal 11 (SIGSEGV) | ||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Curt <bugzilla-qwerty> | ||||||||
| Component: | libreoffice | Assignee: | Caolan McNamara <caolanm> | ||||||||
| Status: | CLOSED INSUFFICIENT_DATA | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||||||
| Severity: | unspecified | Docs Contact: | |||||||||
| Priority: | unspecified | ||||||||||
| Version: | 16 | CC: | caolanm, dtardon, erack, ltinkl, mstahl, sbergman | ||||||||
| Target Milestone: | --- | ||||||||||
| Target Release: | --- | ||||||||||
| Hardware: | x86_64 | ||||||||||
| OS: | Unspecified | ||||||||||
| Whiteboard: | abrt_hash:1400a5e1ced6ff9d33ba87ed802b127be5a1a975 | ||||||||||
| Fixed In Version: | Doc Type: | Bug Fix | |||||||||
| Doc Text: | Story Points: | --- | |||||||||
| Clone Of: | Environment: | ||||||||||
| Last Closed: | 2012-04-18 14:09:37 UTC | Type: | --- | ||||||||
| Regression: | --- | Mount Type: | --- | ||||||||
| Documentation: | --- | CRM: | |||||||||
| Verified Versions: | Category: | --- | |||||||||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||||||
| Cloudforms Team: | --- | Target Upstream Version: | |||||||||
| Attachments: |
|
||||||||||
|
Description
Curt
2012-04-13 19:53:38 UTC
Created attachment 577408 [details]
File: dso_list
Created attachment 577409 [details]
File: maps
Created attachment 577410 [details]
File: backtrace
2048 frames in thread 7 in backtrace already looks suspicious ... endless recursion while disposing a11y until accessing the process that is gone? this is not the first time we've seen this a11y-related backtrace, but we always seem to be unable to reproduce it. Obviously needs a11y to be enabled in the desktop of course. can't reproduce. I know I've seen this type of a11y-related backtrace before though, but couldn't reproduce it then either. If anyone's got a sure-fire way to reproduce this I'd be very interested in squashing this :-( |