Bug 1383902

Summary:	CPU spikes to 100% and timeouts observed in strace when opening yaml extensions using vim
Product:	Red Hat Enterprise Linux 7	Reporter:	Venkata Tadimarri <ktadimar>
Component:	vim	Assignee:	Karsten Hopp <karsten>
Status:	CLOSED ERRATA	QA Contact:	Anna Khaitovich <akhaitov>
Severity:	high	Docs Contact:
Priority:	medium
Version:	7.2	CC:	akhaitov, isenfeld, ktadimar, zdohnal
Target Milestone:	rc	Keywords:	EasyFix, Patch
Target Release:	---
Hardware:	All
OS:	Linux
Whiteboard:
Fixed In Version:	vim-7.4.160-2.el7	Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2017-08-01 20:27:24 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:
Bug Depends On:
Bug Blocks:	1298243, 1393870

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