[email protected]
[Top] [All Lists]

Bug#195719: marked as forwarded (grep: memory leak?)

Subject: Bug#195719: marked as forwarded grep: memory leak?
From: Debian Bug Tracking System
Date: Sat, 10 Dec 2005 17:18:17 -0800
Your message dated Sat, 10 Dec 2005 20:08:28 -0500
with message-id <[email protected]>
has caused the Debian Bug report #195719,
regarding grep: memory leak?
to be marked as having been forwarded to the upstream software
author(s) [email protected]

(NB: If you are a system administrator and have no idea what I am
talking about this indicates a serious mail system misconfiguration
somewhere.  Please contact me immediately.)

Debian bug tracking system administrator
(administrator, Debian Bugs database)

Received: (at 195719-forwarded) by bugs.debian.org; 11 Dec 2005 01:08:33 +0000
>From [email protected] Sat Dec 10 17:08:33 2005
Return-path: <[email protected]>
Received: from ms-smtp-04.nyroc.rr.com ([])
        by spohr.debian.org with esmtp (Exim 4.50)
        id 1ElFhY-00019G-Pv
        for [email protected]; Sat, 10 Dec 2005 17:08:32 -0800
Received: from andromeda (cpe-69-202-136-66.twcny.res.rr.com [])
        by ms-smtp-04.nyroc.rr.com (8.12.10/8.12.10) with ESMTP id 
        Sat, 10 Dec 2005 20:08:30 -0500 (EST)
Received: from pryzbyj by andromeda with local (Exim 4.60)
        (envelope-from <[email protected]>)
        id 1ElFhU-0005uP-SC; Sat, 10 Dec 2005 20:08:29 -0500
Date: Sat, 10 Dec 2005 20:08:28 -0500
To: [email protected]
Cc: [email protected]
Subject: grep -f leaks large amount of memory
Message-ID: <[email protected]>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.5.11
From: Justin Pryzby <[email protected]>
X-Virus-Scanned: Symantec AntiVirus Scan Engine
X-Spam-Checker-Version: SpamAssassin 2.60-bugs.debian.org_2005_01_02 
        (1.212-2003-09-23-exp) on spohr.debian.org
X-Spam-Status: No, hits=-3.0 required=4.0 tests=BAYES_00 autolearn=no 

Please see <http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=195719>
where it is documented that grep -f uses large amounts of memory, and
it is suggested that it might be leaking memory, causing linearly
increasing mem usage.

You can test with:

  grep '^c...............' /usr/share/dict/words >/tmp/words
  grep -f /tmp/words /usr/share/dict/words

The culprit seems to be

   1024816 bytes in 2596 blocks are still reachable in loss record 18 of 18
   at 0x1B90459D: malloc (vg_replace_malloc.c:130)
   by 0x804C5EC: xmalloc (dfa.c:143)
   by 0x804E9BB: build_state (dfa.c:2330)
   by 0x804FC7E: dfaexec (dfa.c:2372)
   by 0x8054DE2: EGexecute (search.c:402)
   by 0x804A6C5: grepbuf (grep.c:732)
   by 0x804B1A5: grepfile (grep.c:851)
   by 0x804C39D: main (grep.c:1788)

(valgrind --leak-check=full --show-reachable=yes 
./build-tree/grep-2.5.1/src/grep -f /tmp/words /usr/share/dict/words)

Clear skies,

To UNSUBSCRIBE, email to [email protected]
with a subject of "unsubscribe". Trouble? Contact [email protected]

<Prev in Thread] Current Thread [Next in Thread>
  • Bug#195719: marked as forwarded (grep: memory leak?), Debian Bug Tracking System <=