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.
Bug 1065370 - huge memory consumption when large background used
Summary: huge memory consumption when large background used
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: gnome-shell
Version: 7.0
Hardware: All
OS: Linux
low
low
Target Milestone: rc
: 7.0
Assignee: Florian Müllner
QA Contact: Desktop QE
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2014-02-14 13:53 UTC by Vladimir Benes
Modified: 2015-11-19 07:12 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2015-11-19 07:12:48 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)
1.2 MB jpeg (1.12 MB, image/jpeg)
2014-02-14 13:54 UTC, Vladimir Benes
no flags Details
317 kB png (309.31 KB, image/png)
2014-02-14 13:54 UTC, Vladimir Benes
no flags Details


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2015:2216 0 normal SHIPPED_LIVE gnome compositor stack bug fix and enhancement update 2015-11-19 08:26:34 UTC

Description Vladimir Benes 2014-02-14 13:53:05 UTC
Description of problem:
I used 10kx10k png (or jpeg) files for background and g-s consumed ~ 3GB + of free ram and oom killer was used. So it was restarted. 

Version-Release number of selected component (if applicable):
gnome-shell-3.8.4-22.el7.x86_64

How reproducible:
always

Steps to Reproduce:
1.fiddle a bit with attached backgrounds

Actual results:
g-s gets restarted by oom killer as it eats all mem

Expected results:
lower memory consumption if < 2MB backgrounds are used

Additional info:

Comment 1 Vladimir Benes 2014-02-14 13:54:25 UTC
Created attachment 863279 [details]
1.2 MB jpeg

Comment 2 Vladimir Benes 2014-02-14 13:54:49 UTC
Created attachment 863280 [details]
317 kB png

Comment 3 RHEL Program Management 2014-03-22 06:01:35 UTC
This request was not resolved in time for the current release.
Red Hat invites you to ask your support representative to
propose this request, if still desired, for consideration in
the next release of Red Hat Enterprise Linux.

Comment 5 Michal Domonkos 2015-05-14 12:20:31 UTC
Not a problem on GNOME-3.14.  Memory consumption is significantly lower and g-s doesn't freeze or restart (as opposed to GNOME-3.8).

Comment 7 errata-xmlrpc 2015-11-19 07:12:48 UTC
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://rhn.redhat.com/errata/RHBA-2015-2216.html


Note You need to log in before you can comment on or make changes to this bug.