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:
running a loop that changes the resolution enlarges the amount of memoty gnome-shell is using.
Version-Release number of selected component (if applicable):
gnome-shell-3.8.4-21.el7.x86_64
Tested on VM with qxl and with cirrus, and on a Lenovo T520 physical machine
How reproducible:
5/5
Steps to Reproduce:
1. On one gnome-terminal run top -p $(pgrep gnome-shell)
2. On a second gnome-terminal run resolution change in a loop (see script below)
3. See memory usage of gnome-shell getting bigger
script:
#!/bin/bash
V=$(xrandr | awk '$2 ~ /^connected/ {print $1}' | head -1)
MODES_TO_CHECK="1024x768 800x600 1440x900 640x480 1280x1024"
MODES=""
for m in $MODES_TO_CHECK; do
if xrandr | grep -q $m; then
MODES="$MODES $m"
fi
done
function setmode () {
xrandr --output $V --mode $1
sleep 3
}
for i in $(req 1 100); do
for m in $MODES; do
echo $i $m
setmode $m
done
done
Actual results:
Memory used is getting larger
Expected results:
Memory used is not getting larger
Installed using RHEL-7.0-20140127.0-Client-x86_64-boot.iso
Comment 3RHEL Program Management
2014-03-22 06:07:59 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.
Description of problem: running a loop that changes the resolution enlarges the amount of memoty gnome-shell is using. Version-Release number of selected component (if applicable): gnome-shell-3.8.4-21.el7.x86_64 Tested on VM with qxl and with cirrus, and on a Lenovo T520 physical machine How reproducible: 5/5 Steps to Reproduce: 1. On one gnome-terminal run top -p $(pgrep gnome-shell) 2. On a second gnome-terminal run resolution change in a loop (see script below) 3. See memory usage of gnome-shell getting bigger script: #!/bin/bash V=$(xrandr | awk '$2 ~ /^connected/ {print $1}' | head -1) MODES_TO_CHECK="1024x768 800x600 1440x900 640x480 1280x1024" MODES="" for m in $MODES_TO_CHECK; do if xrandr | grep -q $m; then MODES="$MODES $m" fi done function setmode () { xrandr --output $V --mode $1 sleep 3 } for i in $(req 1 100); do for m in $MODES; do echo $i $m setmode $m done done Actual results: Memory used is getting larger Expected results: Memory used is not getting larger