Zsh Mailing List Archive
Messages sorted by:
Reverse Date,
Date,
Thread,
Author
Re: Valgrind tests (was: Re: Zsh: [7] + 23074 suspended (tty output))
- X-seq: zsh-workers 44524
- From: Peter Stephenson <p.stephenson@xxxxxxxxxxx>
- To: <zsh-workers@xxxxxxx>
- Subject: Re: Valgrind tests (was: Re: Zsh: [7] + 23074 suspended (tty output))
- Date: Mon, 15 Jul 2019 10:29:17 +0100
- Cms-type: 201P
- Dkim-filter: OpenDKIM Filter v2.11.0 mailout2.w1.samsung.com 20190715092920euoutp023aefd25cd1d1f6a80fb5e4d9df0c6db7~xip7B-BjQ2799527995euoutp021
- Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=samsung.com; s=mail20170921; t=1563182960; bh=ZE/m5CnH+49AKiluHkadCBJMR4IiYbfVQrPwTj2oTx0=; h=Subject:From:To:Date:In-Reply-To:References:From; b=E9KJZ2BqBBZ2uwwZl8v3D4PLLk6eD6K92WZroa4Fll4PM15HaM2fuBRqupU9Mc2Yv PurBp+fa8ZMFreHkFlTr8apOqcriDgK5dvCno2CCnGCrsnzQE/O4bs105Pj7oltoIg 7kdy2mNMW2AP5YwU2jC52Ns0cCZtC1YalM45iljQ=
- In-reply-to: <CAKc7PVDFnYkS4sX+==ivpyegO4t5TUh_752u6-x-bPV+bg1SPA@mail.gmail.com>
- List-help: <mailto:zsh-workers-help@zsh.org>
- List-id: Zsh Workers List <zsh-workers.zsh.org>
- List-post: <mailto:zsh-workers@zsh.org>
- List-unsubscribe: <mailto:zsh-workers-unsubscribe@zsh.org>
- Mailing-list: contact zsh-workers-help@xxxxxxx; run by ezmlm
- References: <ef42fe7f-4ecf-4dbc-cdb0-2d6e4cf27377@xk2c.de> <CAKc7PVAsJXv=jxcbrENM4LtcBkz86mbVe3WgCYBs6cwdEO=9hQ@mail.gmail.com> <1537195773.3258650.1510860136.6AA9F0BA@webmail.messagingengine.com> <CAKc7PVD0aoqenFzNeo-3HitqAtxi27-t=EcNQwc4=t57SYs0Hg@mail.gmail.com> <1537286139.1154549.1512322472.101174D6@webmail.messagingengine.com> <CGME20190703233057epcas1p13bb98039bcf029279b8806a3cb353419@epcas1p1.samsung.com> <CAKc7PVDFnYkS4sX+==ivpyegO4t5TUh_752u6-x-bPV+bg1SPA@mail.gmail.com>
On Thu, 2019-07-04 at 01:29 +0200, Sebastian Gniazdowski wrote:
> The tests apparently reveal one memory leak currently:
>
> ==52847== 79 (24 direct, 55 indirect) bytes in 1 blocks are definitely
> lost in loss record 349 of 550
> ==52847== at 0x10017B545: malloc (vg_replace_malloc.c:302)
> ==52847== by 0x10004899E: zalloc (mem.c:966)
> ==52847== by 0x10004316D: znewlinklist (linklist.c:120)
> ==52847== by 0x10003989D: addfilelist (jobs.c:1297)
> ==52847== by 0x100017AC0: getoutputfile (exec.c:4796)
> ==52847== by 0x100078474: stringsubst (subst.c:254)
> ==52847== by 0x100077E46: prefork (subst.c:142)
> ==52847== by 0x10001A24F: execfuncdef (exec.c:2567)
> ==52847== by 0x10001DC23: execcmd_exec (exec.c:3896)
> ==52847== by 0x10001AAF6: execpline2 (exec.c:1927)
> ==52847== by 0x100015938: execpline (exec.c:1658)
> ==52847== by 0x1000150E2: execlist (exec.c:1413)
By the way, I think these are benign --- addfilelist() adds a file to be
tidied up when a job exits, but these appear to happening in subshells.
This means there's no job clear-up --- but the shell simply exits. So
the memory isn't recovered in the subshell but that doesn't cause a
long-term build-up.
I haven't followed every single one of this type, though.
pws
Messages sorted by:
Reverse Date,
Date,
Thread,
Author