Bug 86296

Summary: huge memory leak in watch
Product: [Retired] Red Hat Linux Reporter: Adam Thompson <athompso>
Component: procpsAssignee: Alexander Larsson <alexl>
Status: CLOSED WORKSFORME QA Contact: Brian Brock <bbrock>
Severity: high Docs Contact:
Priority: medium    
Version: 8.0   
Target Milestone: ---   
Target Release: ---   
Hardware: i386   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2003-08-21 21:17:44 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Adam Thompson 2003-03-19 04:51:42 UTC
From Bugzilla Helper:
User-Agent: Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.1; .NET CLR 
1.0.3705)

Description of problem:
use of 'watch' utility to watch *any* program's output appears to cause it to 
use up memory at a rate of approximately 1 Mbyte/sec.

This naturally causes system instability when one leaves watch running in a 
terminal during a long (overnight) process...


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

How reproducible:
Always

Steps to Reproduce:
1. run 'watch' agains any program
2. watch RAM leak away...
3. use reset button to reboot system
    

Additional info:

Comment 1 Alexander Larsson 2003-03-19 08:23:53 UTC
I don't see this in 2.0.11-4. Can you test the version in RAWHIDE?


Comment 2 Adam Thompson 2003-08-21 21:17:44 UTC
cannot reproduce in RH9.0 or 2.1AS, and I no longer have any RH8.0 system