Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Descriptionprashant ingale
2011-04-14 11:32:46 UTC
Created attachment 492059[details]
backtrace
Description of problem:
metacity was killed by signal 11 pa_memblock_unref
reason: Process /usr/bin/metacity was killed by signal 11 (SIGSEGV)
Version-Release number of selected component (if applicable):
architecture: i686
executable: /usr/bin/metacity
package: metacity-2.28.0-20.el6
release: Red Hat Enterprise Linux Server release 6.0 (Santiago)
How reproducible:
randomly
Steps to Reproduce:
1.
2.
3.
Actual results:
metacity crashed
Expected results:
metacity should not crashed
Additional info:
Comment 2RHEL Program Management
2011-07-06 01:00:16 UTC
This request was evaluated by Red Hat Product Management for
inclusion in the current release of Red Hat Enterprise Linux.
Because the affected component is not scheduled to be updated
in the current release, Red Hat is unfortunately unable to
address this request at this time. Red Hat invites you to
ask your support representative to propose this request, if
appropriate and relevant, in the next release of Red Hat
Enterprise Linux. If you would like it considered as an
exception in the current release, please ask your support
representative.
Comment 8RHEL Program Management
2013-07-16 08:19:24 UTC
This request was evaluated by Red Hat Product Management for
inclusion in the current release of Red Hat Enterprise Linux.
Because the affected component is not scheduled to be updated
in the current release, Red Hat is unable to address this
request at this time.
Red Hat invites you to ask your support representative to
propose this request, if appropriate, in the next release of
Red Hat Enterprise Linux.
This issue is reproduced even with the latest packages in customer's system.
- pulseaudio-0.9.21-24.el6.x86_64
- metacity-2.28.0-23.el6.x86_64
- glib2-2.28.8-5.el6.x86_64
- glibc-2.12-1.192.el6.x86_64
(gdb) bt
#0 pa_atomic_load (b=0x7fe3dbb8f000) at pulsecore/atomic.h:57
#1 pa_memblock_unref (b=0x7fe3dbb8f000) at pulsecore/memblock.c:589
#2 0x00007fe3e0c50912 in item_free (item=0x7fe3d4001a50, q=<value optimized out>) at pulsecore/pstream.c:292
#3 0x00007fe3e0c52a5a in pa_queue_free (q=0x7fe3d4000b10, free_func=0x7fe3e0c508a0 <item_free>, userdata=0x0) at pulsecore/queue.c:61
#4 0x00007fe3e0c50a4f in pstream_free (p=0x7fe3d4000960) at pulsecore/pstream.c:307
#5 pa_pstream_unref (p=0x7fe3d4000960) at pulsecore/pstream.c:956
#6 0x00007fe3e0c50c84 in do_something (p=0x7fe3d4000960) at pulsecore/pstream.c:203
#7 0x00007fe3e0e92b4c in dispatch_pollfds (m=0x1df83b0) at pulse/mainloop.c:688
#8 pa_mainloop_dispatch (m=0x1df83b0) at pulse/mainloop.c:933
#9 0x00007fe3e0e92ed8 in pa_mainloop_iterate (m=0x1df83b0, block=<value optimized out>, retval=0x0) at pulse/mainloop.c:964
#10 0x00007fe3e0e92f80 in pa_mainloop_run (m=0x1df83b0, retval=0x0) at pulse/mainloop.c:979
#11 0x00007fe3e0ea1a4b in thread (userdata=0x1df40f0) at pulse/thread-mainloop.c:94
#12 0x00007fe3e0c5e9b8 in internal_thread_func (userdata=0x1df86c0) at pulsecore/thread-posix.c:72
#13 0x00007fe3eacc8aa1 in start_thread (arg=0x7fe3dbb7e700) at pthread_create.c:301
#14 0x00007fe3ebe29aad in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:115
Comment 21Red Hat Bugzilla
2023-09-14 01:23:34 UTC
The needinfo request[s] on this closed bug have been removed as they have been unresolved for 1000 days
Created attachment 492059 [details] backtrace Description of problem: metacity was killed by signal 11 pa_memblock_unref reason: Process /usr/bin/metacity was killed by signal 11 (SIGSEGV) Version-Release number of selected component (if applicable): architecture: i686 executable: /usr/bin/metacity package: metacity-2.28.0-20.el6 release: Red Hat Enterprise Linux Server release 6.0 (Santiago) How reproducible: randomly Steps to Reproduce: 1. 2. 3. Actual results: metacity crashed Expected results: metacity should not crashed Additional info: