Bug 810426
| Summary: | [abrt] gnome-shell-3.2.2.1-1.fc16: g_malloc0: Process /usr/bin/gnome-shell was killed by signal 6 (SIGABRT) | ||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Tim Zorn <timothy.zorn> | ||||||||||||
| Component: | gnome-shell | Assignee: | Owen Taylor <otaylor> | ||||||||||||
| Status: | CLOSED DUPLICATE | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||||||||||
| Severity: | unspecified | Docs Contact: | |||||||||||||
| Priority: | unspecified | ||||||||||||||
| Version: | 16 | CC: | maxamillion, otaylor, samkraju, walters | ||||||||||||
| Target Milestone: | --- | ||||||||||||||
| Target Release: | --- | ||||||||||||||
| Hardware: | x86_64 | ||||||||||||||
| OS: | Unspecified | ||||||||||||||
| Whiteboard: | abrt_hash:7a922ce594bfc800f733490a0c0138372c260366 | ||||||||||||||
| Fixed In Version: | Doc Type: | Bug Fix | |||||||||||||
| Doc Text: | Story Points: | --- | |||||||||||||
| Clone Of: | 702257 | Environment: | |||||||||||||
| Last Closed: | 2012-04-06 14:08:05 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
Tim Zorn
2012-04-06 04:00:52 UTC
Created attachment 575602 [details]
File: dso_list
Created attachment 575603 [details]
File: build_ids
Created attachment 575604 [details]
File: maps
Created attachment 575605 [details]
File: var_log_messages
Created attachment 575606 [details]
File: backtrace
Unfortunately, this backtrace isn't more useful- it just shows a crash from memory corruption at some previous time. If you *are not* using FGLRX and have some reliable way of reproducing a crash with Fedora 16, I'm interested in that, however. *** Bug 810479 has been marked as a duplicate of this bug. *** You may have said this elsewhere, but are you using any GNOME Shell extensions? (From the command line '$ gsettings get org.gnome.shell enabled-extensions') Oh, I see fglrx from your comments on the other bug. (Note that bug 702257 combines a well known, though not debugged, fglrx crash with other crashes that aren't from fglrx but end up with similar backtraces so ABRT combines them - confusing.) A good valgrind log could have a smoking gun, but valgrinding GNOME Shell is quite tricky - the problem is that valgrind doesn't get everything right - so any real errors are lost in a sea of false positives - so you either have to have a well tuned "suppressions file" or dump out everything and be skilled at extracting the real errors from the false positives. *** This bug has been marked as a duplicate of bug 702257 *** Owen Taylor, how soon after running in valgrind should it crash to be useful. I've got it down to be able to reproduce soft of reliably. |