From: "vries at gcc dot gnu.org" <sourceware-bugzilla@sourceware.org>
To: dwz@sourceware.org
Subject: [Bug default/27643] [dwz] build_abbrevs memory leak
Date: Wed, 24 Mar 2021 09:06:15 +0000 [thread overview]
Message-ID: <bug-27643-11298-wzkIPdUXBC@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-27643-11298@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=27643
Tom de Vries <vries at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Summary|[dwz] more low mem memory |[dwz] build_abbrevs memory
|leaks |leak
--- Comment #2 from Tom de Vries <vries at gcc dot gnu.org> ---
OK, the test run was on top of a few proposed patches, which moves the
dwz_with_low_mem call into a separate process, such that we only see the
problem later, which explains why we don't see dwz_with_low_mem in comment 0.
On trunk, we do get dwz_with_low_mem instead of dwz:
...
Direct leak of 432 byte(s) in 6 object(s) allocated from:
#0 0x7f8d6a37d6d8 in __interceptor_calloc (/usr/lib64/libasan.so.4+0xdc6d8)
#1 0x475e34 in htab_try_create /home/vries/dwz/dwz.git/hashtab.c:164
#2 0x44c610 in build_abbrevs /home/vries/dwz/dwz.git/dwz.c:11230
#3 0x44ee00 in compute_abbrevs /home/vries/dwz/dwz.git/dwz.c:11510
#4 0x46f07c in dwz /home/vries/dwz/dwz.git/dwz.c:15396
#5 0x4748f5 in dwz_with_low_mem /home/vries/dwz/dwz.git/dwz.c:16274
#6 0x474eb5 in dwz_files_1 /home/vries/dwz/dwz.git/dwz.c:16343
#7 0x47570c in dwz_files /home/vries/dwz/dwz.git/dwz.c:16427
#8 0x475a6f in main /home/vries/dwz/dwz.git/dwz.c:16468
#9 0x7f8d69cf2349 in __libc_start_main (/lib64/libc.so.6+0x24349)
...
Anyway, looks like the problem is not specific to low-mem, adapting summary.
--
You are receiving this mail because:
You are on the CC list for the bug.
next prev parent reply other threads:[~2021-03-24 9:06 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-24 8:40 [Bug default/27643] New: [dwz] more low mem memory leaks vries at gcc dot gnu.org
2021-03-24 8:43 ` [Bug default/27643] " vries at gcc dot gnu.org
2021-03-24 9:06 ` vries at gcc dot gnu.org [this message]
2021-03-24 10:52 ` [Bug default/27643] [dwz] build_abbrevs memory leak vries at gcc dot gnu.org
2021-03-24 17:08 ` vries at gcc dot gnu.org
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=bug-27643-11298-wzkIPdUXBC@http.sourceware.org/bugzilla/ \
--to=sourceware-bugzilla@sourceware.org \
--cc=dwz@sourceware.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).