Bug 1306099

Summary: vim goes into endless loop when fatal signal hits in deathtrap signal handler
Product: Red Hat Enterprise Linux 6 Reporter: Jay Shin <jaeshin>
Component: vimAssignee: Zdenek Dohnal <zdohnal>
Status: CLOSED WONTFIX QA Contact: BaseOS QE - Apps <qe-baseos-apps>
Severity: high Docs Contact:
Priority: high    
Version: 6.7CC: bhubbard, cww, dkochuka, jaeshin, jwright, karsten
Target Milestone: rc   
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of:
: 1450562 (view as bug list) Environment:
Last Closed: 2017-08-15 18:58:52 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: 1269194, 1450562    

Description Jay Shin 2016-02-10 01:50:10 UTC
Description of problem:
  abrt-action-generate-core-backtrace consumed all memory resources after vim killed
  

Version-Release number of selected component (if applicable):
ENVIRONMENT:
  PowerEdge R920     Vers: 1.0.7    Date: 02/24/2014    BIOS Rev: 1.0
  Intel(R) Xeon(R) CPU E7-4880 v2 @ 2.50GHz / 256 GB Memory
  Vxfs Oracle server
  2.6.32-573.3.1.el6.x86_64
  vim-enhanced-7.4.629-5.el6
  abrt-2.0.8-34.el6.x86_64

How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:
  abrt-action-generate-core-backtrace consumed all memory resources
  
Expected results:
  abrt process should not consume all memory resources.

Additional info:
  see the following comment for more details.

Comment 4 Brad Hubbard 2016-02-12 06:28:49 UTC
The abrt issue is being dealt with in bz1306903. This bug is for the vim crash.