From owner-freebsd-stable Thu Sep 27 12: 1:14 2001 Delivered-To: freebsd-stable@freebsd.org Received: from logicalhost.com (logicalhost.com [63.169.206.2]) by hub.freebsd.org (Postfix) with ESMTP id CF05A37B40C for ; Thu, 27 Sep 2001 12:01:11 -0700 (PDT) Received: from localhost (diesel@localhost) by logicalhost.com (8.11.6/8.11.6) with ESMTP id f8RJ2Rr50539 for ; Thu, 27 Sep 2001 15:02:27 -0400 (EDT) Date: Thu, 27 Sep 2001 15:02:27 -0400 (EDT) From: raymond hicks X-X-Sender: To: Subject: possible mem leak in command "top"? Message-ID: <20010927144914.P50404-100000@logicalhost.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Has anyone else noticed memory leak when running the command "top"? I noticed there were NO free CPU cycles on my box (4.3-stable) 2 days ago. Listing process showed top had been running for over 24 hours and was using 99% of CPU. I killed that process and started top again. This time I let it run for just under an hour. In that time it accelerated from using at start just under 2% of CPU to over 44% after I finally killed it. What is also interesting is when you kill the process, the display goes away but ps still shows the process about 20 % of the time>?? Any input is appreciated. Raymond hicks To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message