| Summary: | [abrt] xfce4-mixer-4.8.0-1.fc16: __GI___libc_malloc: Process /usr/libexec/xfce4/panel-plugins/xfce4-mixer-plugin was killed by signal 6 (SIGABRT) | ||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Mike C <mike.cloaked> | ||||||||||||
| Component: | xfce4-mixer | Assignee: | Kevin Fenzi <kevin> | ||||||||||||
| Status: | CLOSED NEXTRELEASE | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||||||||||
| Severity: | unspecified | Docs Contact: | |||||||||||||
| Priority: | unspecified | ||||||||||||||
| Version: | 16 | CC: | kevin | ||||||||||||
| Target Milestone: | --- | ||||||||||||||
| Target Release: | --- | ||||||||||||||
| Hardware: | i686 | ||||||||||||||
| OS: | Unspecified | ||||||||||||||
| Whiteboard: | abrt_hash:4bf01ffca3b0c065bf25e44606ed93f4498e782e | ||||||||||||||
| Fixed In Version: | Doc Type: | Bug Fix | |||||||||||||
| Doc Text: | Story Points: | --- | |||||||||||||
| Clone Of: | Environment: | ||||||||||||||
| Last Closed: | 2012-01-08 15:57:34 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
Mike C
2011-12-17 19:38:25 UTC
Created attachment 548254 [details]
File: dso_list
Created attachment 548255 [details]
File: maps
Created attachment 548256 [details]
File: backtrace
Did this just happen the one time? Or does it crash this way everytime? On the day I reported this it happened every time - I have not used the machine since then (an NC10 netbook) but I can check again this evening. The behaviour is entirely reproducable - I also noticed that the .xsession-errors file contains: *** glibc detected *** xfce4-mixer: free(): invalid next size (normal): 0x089d74b0 *** ======= Backtrace: ========= /lib/libc.so.6[0x415a1d22] and many other lines. I will attach the full file shortly - I don't know if it adds to the info from the previous files in this report. However this may be a glibc problem rather than an xfce4-mixer problem? Created attachment 548684 [details]
.s
Created attachment 548685 [details]
.xsession-errors with lines relevant to the xfce4-mixer problem
Possible glibc connection?
A long shot but is this related at all? https://bugzilla.redhat.com/show_bug.cgi?format=multiple&id=757953 I decided to restore the entire user area from backup - this time when I logged in the abrt threw a different but similar error this time related to gst-plugins-scanner: from .xsession-errors: *** glibc detected *** /usr/libexec/gstreamer-0.10/gst-plugin-scanner: malloc(): memory corruption: 0x08846b00 *** ======= Backtrace: ========= /lib/libc.so.6[0x415a1d22] /lib/libc.so.6[0x415a3e02] /lib/libc.so.6(__libc_malloc+0x65)[0x415a61a5] /usr/lib/liborc-0.4.so.0(orc_code_region_allocate_codemem_dual_map+0xdc)[0x2fc16c] /usr/lib/liborc-0.4.so.0(orc_code_region_allocate_codemem+0x8e)[0x2fc4be] I do have gstreamer-plugins-good and gstreamer-plugins-bad installed from rpmfusion - is that a possible factor? I tried to start Amarok - and now get the following in the .xsession-errors file: *** glibc detected *** /usr/libexec/gstreamer-0.10/gst-plugin-scanner: malloc(): memory corruption: 0x099bfb00 *** ======= Backtrace: ========= /lib/libc.so.6[0x415a1d22] /lib/libc.so.6[0x415a3e02] /lib/libc.so.6(__libc_malloc+0x65)[0x415a61a5] I ran the abrt analysis with retrace server. During the analyse stage however it gave: Initializing virtual root Generating backtrace Retrace job finished successfully Backtrace parsing failed for . 1:0: No frame and no thread found. Presume this may be due to the gstreamer-plugins-* from rpmfusion? So I aborted the abrt reporting since the backtrace was unusable. I am guessing this is related to the original bug somehow? Anything else I can do without downloading hundreds of megabytes of debuginfo files? This looks like possibly another case of: https://bugzilla.redhat.com/show_bug.cgi?id=757953 https://bugzilla.redhat.com/show_bug.cgi?id=759809 is related and package orc-0.4.16-5.fc17.i686 Fixes this for me. https://bugzilla.redhat.com/show_bug.cgi?id=768668 may be related in which case package orc-0.4.16-5.fc17.i686 may fix this for you also. It certainly fixes it for me. Whoops - sorry comment #14 should have been entered for a related bug! Sorry for the noise on that. |