[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: memory leak in execute_simple_command when dofork is true
From: |
Chet Ramey |
Subject: |
Re: memory leak in execute_simple_command when dofork is true |
Date: |
Fri, 4 Nov 2016 14:20:39 -0400 |
User-agent: |
Mozilla/5.0 (Macintosh; Intel Mac OS X 10.11; rv:45.0) Gecko/20100101 Thunderbird/45.4.0 |
On 11/4/16 12:35 AM, Eduardo A. Bustamante López wrote:
> I ran the configure script with the following arguments:
>
> hp% ./configure CC=gcc-6 CFLAGS='-Wall -g -ggdb -O0 -fsanitize=address'
> LDFLAGS=-fsanitize=address --without-bash-malloc
>
> Which enables the LeakSanitizer
> (https://github.com/google/sanitizers/wiki/AddressSanitizerLeakSanitizer).
>
> It detected the following memory leak:
It `leaks' in the child process. The parent eventually stores that memory
in the jobs list and frees it when the job is deleted. The leaks don't
accumulate; they are individual to each child process. It's never been a
big deal in practice.
Chet
--
``The lyf so short, the craft so long to lerne.'' - Chaucer
``Ars longa, vita brevis'' - Hippocrates
Chet Ramey, UTech, CWRU chet@case.edu http://cnswww.cns.cwru.edu/~chet/