Bug 1383902 - CPU spikes to 100% and timeouts observed in strace when opening yaml extensions using vim
Summary: CPU spikes to 100% and timeouts observed in strace when opening yaml extensio...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: vim
Version: 7.2
Hardware: All
OS: Linux
medium
high
Target Milestone: rc
: ---
Assignee: Karsten Hopp
QA Contact: Anna Khaitovich
URL:
Whiteboard:
Depends On:
Blocks: 1298243 1393870
TreeView+ depends on / blocked
 
Reported: 2016-10-12 06:23 UTC by Venkata Tadimarri
Modified: 2020-09-10 09:50 UTC (History)
4 users (show)

Fixed In Version: vim-7.4.160-2.el7
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2017-08-01 20:27:24 UTC
Target Upstream Version:

Attachments (Terms of Use)
Add an attachment (proposed patch, testcase, etc.)


Links
System ID Private Priority Status Summary Last Updated
Github /chase vim-ansible-yaml issues 11 0 None None None 2020-03-25 13:59:57 UTC
Red Hat Product Errata RHBA-2017:1879 0 normal SHIPPED_LIVE vim bug fix update 2017-08-01 18:25:01 UTC

Description Venkata Tadimarri 2016-10-12 06:23:13 UTC 
Description of problem:

When opening yaml extension files using vim, the cpu spikes to 100% and strace shows Timeouts. 

This has been mostly observed with files having ssh keys as compared to files without them.

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

vim-enhanced-7.4.160-1.el7.x86_64

How reproducible:

Any .yaml files with the ssh keys just display a blank screen and the only way is to kill the process from a different session. 

Steps to Reproduce:
1. Download the attached .yaml file
2. Use vim to open the file
3.

Actual results:

Blank screen and CPU spike. 

Expected results:


Editor should show the content of the file

Additional info:
Comment 13 Zdenek Dohnal 2016-12-09 09:21:13 UTC 
Thank you for response, Krishna. Proposing this bug as EasyFix.
Comment 20 errata-xmlrpc 2017-08-01 20:27:24 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://access.redhat.com/errata/RHBA-2017:1879
Note You need to log in before you can comment on or make changes to this bug.