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:
When 'Exceed on Demand' application is used to connect RHEL7 server and run gvim, gvim processes were monitored to be using CPU up to 100%.
I was able to reproduce that phenomenon which is described below.
Version-Release number of selected component (if applicable):
libX11-1.6.7-2.el7.x86_64
libX11-common-1.6.7-2.el7.noarch
vim-X11-7.4.629-6.el7.x86_64
vim-common-7.4.629-6.el7.x86_64
vim-enhanced-7.4.629-6.el7.x86_64
How reproducible:
always under certain condition
Steps to Reproduce:
1. setup XDMCP server as described at https://access.redhat.com/solutions/2736
2. run gvim from a remote client
# ssh -X xdemcp_server -l yourid gvim
3. check file descriptor information of the running gvim process and take a note on the fd of anon_inode:[eventfd]
# ls -al /proc/`pidof gvim`/fd
dr-x------. 2 hwanii hwanii 0 5ì 4 16:03 .
dr-xr-xr-x. 9 hwanii hwanii 0 5ì 4 16:03 ..
lrwx------. 1 hwanii hwanii 64 5ì 4 16:03 0 -> /dev/pts/1
lrwx------. 1 hwanii hwanii 64 5ì 4 16:03 1 -> /dev/pts/1
lrwx------. 1 hwanii hwanii 64 5ì 4 16:03 2 -> /dev/pts/1
lrwx------. 1 hwanii hwanii 64 5ì 4 16:03 4 -> /home/hwanii/.test.swp
lrwx------. 1 hwanii hwanii 64 5ì 4 16:03 5 -> socket:[42592]
lrwx------. 1 hwanii hwanii 64 5ì 4 16:03 6 -> anon_inode:[eventfd] <==========
4. closed the anon_inode which was fd 6.
# gdb -batch -p $(pidof gvim) -ex "call close(6)" -ex cont -ex quit
Actual results:
the gvim process starts using 100% CPU.
Expected results:
gvim process should not use high CPU utilization.
Additional info:
I am not sure if the condition will never be met when users only run software shipped by Red Hat as there was XDMCP of lightdm running in the customer environment.
Hi,
The customer (Hyundai Autron Co., Ltd.) mentioned that more companies are upgrading their OS from RHEL5 or 6 to RHEL7 to run applications for semi-conduct design in semi-conduct industry, hoping this bug to be addressed.
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 (vim bug fix and enhancement update), 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://access.redhat.com/errata/RHBA-2020:5432