Bug 1820631

Summary: poor performance when moving windows
Product: Red Hat Enterprise Linux 8 Reporter: Joe Wright <jwright>
Component: mutterAssignee: Jonas Ã…dahl <jadahl>
Status: CLOSED MIGRATED QA Contact: Peter Kopec <pekopec>
Severity: high Docs Contact:
Priority: high    
Version: 8.5CC: alanm, amike, brclark, fmuellner, gkeegan, jadahl, jkoten, jreznik, kwalker, mclasen, mkolbas, pekopec, sbarcomb, tpelka, tpopela
Target Milestone: rcKeywords: MigratedToJIRA, Reopened, Triaged
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2023-09-17 14:52:14 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
screenshot from htop none

Description Joe Wright 2020-04-03 13:34:15 UTC
Description of problem:
cpu consumption spikes when moving around windows

Version-Release number of selected component (if applicable):
7.8 GA

How reproducible:
100% by customer

Steps to Reproduce:
1. Install RHEL on a system with a Nvidia GPU
2. Install Nvidia proprietary driver
3. Drag a window around
4. observe CPU consumption

Actual results:
- 70%+ cpu consumption

Expected results:
- very low CPU usage

Additional info:
- persists after patch for bz1737515

Comment 3 Joe Wright 2020-04-03 13:39:11 UTC
Created attachment 1676010 [details]
screenshot from htop

Comment 16 Chris Williams 2020-11-11 21:52:41 UTC
Red Hat Enterprise Linux 7 shipped it's final minor release on September 29th, 2020. 7.9 was the last minor releases scheduled for RHEL 7.
From intial triage it does not appear the remaining Bugzillas meet the inclusion criteria for Maintenance Phase 2 and will now be closed. 

From the RHEL life cycle page:
https://access.redhat.com/support/policy/updates/errata#Maintenance_Support_2_Phase
"During Maintenance Support 2 Phase for Red Hat Enterprise Linux version 7,Red Hat defined Critical and Important impact Security Advisories (RHSAs) and selected (at Red Hat discretion) Urgent Priority Bug Fix Advisories (RHBAs) may be released as they become available."

If this BZ was closed in error and meets the above criteria please re-open it flag for 7.9.z, provide suitable business and technical justifications, and follow the process for Accelerated Fixes:
https://source.redhat.com/groups/public/pnt-cxno/pnt_customer_experience_and_operations_wiki/support_delivery_accelerated_fix_release_handbook  

Feature Requests can re-opened and moved to RHEL 8 if the desired functionality is not already present in the product. 

Please reach out to the applicable Product Experience Engineer[0] if you have any questions or concerns.  

[0] https://bugzilla.redhat.com/page.cgi?id=agile_component_mapping.html&product=Red+Hat+Enterprise+Linux+7

Comment 18 Chris Williams 2020-11-11 23:16:31 UTC
Apologies for the inadvertent closure.

Comment 24 Tomas Popela 2021-06-21 13:20:38 UTC
Moving this to mutter as the test changes were done there.

Comment 32 RHEL Program Management 2023-09-17 14:51:37 UTC
Issue migration from Bugzilla to Jira is in process at this time. This will be the last message in Jira copied from the Bugzilla bug.

Comment 33 RHEL Program Management 2023-09-17 14:52:14 UTC
This BZ has been automatically migrated to the issues.redhat.com Red Hat Issue Tracker. All future work related to this report will be managed there.

Due to differences in account names between systems, some fields were not replicated.  Be sure to add yourself to Jira issue's "Watchers" field to continue receiving updates and add others to the "Need Info From" field to continue requesting information.

To find the migrated issue, look in the "Links" section for a direct link to the new issue location. The issue key will have an icon of 2 footprints next to it, and begin with "RHEL-" followed by an integer.  You can also find this issue by visiting https://issues.redhat.com/issues/?jql= and searching the "Bugzilla Bug" field for this BZ's number, e.g. a search like:

"Bugzilla Bug" = 1234567

In the event you have trouble locating or viewing this issue, you can file an issue by sending mail to rh-issues. You can also visit https://access.redhat.com/articles/7032570 for general account information.