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.

Description of problem:
abrt version: 1.1.13
architecture: i686
Attached file: backtrace
cmdline: metacity --sm-client-id 105387d5d71381214f129126774077385000000020290025
component: metacity
executable: /usr/bin/metacity
reason: Process /usr/bin/metacity was killed by signal 6 (SIGABRT)


Version-Release number of selected component (if applicable):
Red Hat Enterprise Linux Client release 6.0 (Santiago)
metacity-2.28.0-20.el6
kernel: 2.6.32-71.7.1.el6.i686


How reproducible:
random crash.

Steps to Reproduce:
1.
2.
3.
  
Actual results:
Metacity was killed.

Expected results:
Metacity should not killed.

Additional info:

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.

Without reproduction instructions, it would be very hard to fix this. The reported error here is a out-of-memory inside the X server, which could just be the result of the machine running out of memory, or could be a result of a client application creating a window that is very, very big (nearly as big as the X window size limits of 16,000 pixels).

Development Management has reviewed and declined this request.  You may appeal
this decision by reopening this request.