From owner-freebsd-hackers Thu Oct 4 11:39:51 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from mass.dis.org (mass.dis.org [216.240.45.41]) by hub.freebsd.org (Postfix) with ESMTP id 799ED37B401 for ; Thu, 4 Oct 2001 11:39:48 -0700 (PDT) Received: from mass.dis.org (localhost [127.0.0.1]) by mass.dis.org (8.11.6/8.11.3) with ESMTP id f94InnE01299; Thu, 4 Oct 2001 11:49:50 -0700 (PDT) (envelope-from msmith@mass.dis.org) Message-Id: <200110041849.f94InnE01299@mass.dis.org> X-Mailer: exmh version 2.1.1 10/15/1999 To: Guido van Rooij Cc: freebsd-hackers@freebsd.org Subject: Re: grep memory footage In-reply-to: Your message of "Thu, 04 Oct 2001 18:03:56 +0200." <20011004180356.A76896@gvr.gvr.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 04 Oct 2001 11:49:49 -0700 From: Mike Smith Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG > > When fgrepping a huge file (say 10GB) for a non-existing string, > fgrep's memory size skyrockets. At a certain point in time its SIZE was 391M > (RSS was about 30MB) and the system got rather unreponsive. The > string was about 12 bytes big, and we fail to see why grep would > need so much. > > Is there a good explanation for this? It's a known bug in grep; there are probably a bunch of PRs outstanding on it. We need grep to be updated. -- ... every activity meets with opposition, everyone who acts has his rivals and unfortunately opponents also. But not because people want to be opponents, rather because the tasks and relationships force people to take different points of view. [Dr. Fritz Todt] V I C T O R Y N O T V E N G E A N C E To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message