From: Ivan Sorokin <vanyacpp@gmail.com>
To: Jaroslav Kysela <perex@perex.cz>
Cc: alsa-devel@alsa-project.org
Subject: Re: possibly memory leak in alsa-lib
Date: Wed, 31 Oct 2012 01:36:09 +0400 [thread overview]
Message-ID: <50904849.5030101@gmail.com> (raw)
In-Reply-To: <20121030114835.5cb85160@t510.perex-int.cz>
On 30.10.2012 14:48, Jaroslav Kysela wrote:
> On Tue, 30 Oct 2012 02:12:55 +0400
> Ivan Sorokin <vanyacpp@gmail.com> wrote:
>
>> The following program shows a few leaks in valgrind (ubuntu 12.04,
>> alsa-lib 1.0.25, eglibc 2.15):
>>
>> I'm not sure, but probably some leaks are caused by glibc.
>
> Most of them are glibc leaks, but I found a little issue in alsa-lib,
> too. This commit should fix it:
>
> http://git.alsa-project.org/?p=alsa-lib.git;a=commitdiff;h=edcd677bf2065c560ef578940bab8f0aacddf0e6
Thank you very much. I looked into those leaks in glibc and they
appeared to be fixed (at least some of them):
http://sourceware.org/git/?p=glibc.git;a=commitdiff;h=d44638b0a7fc1f01c3b2153cfa1bbb849f01f217;hp=da0331a873dbb62462c151c3d824da2f6fe2e770
Sadly this fix is in 2.16 and ubuntu 12.04 is shipped with glibc 2.15.
When I get next version of glibc, I will check my program again.
prev parent reply other threads:[~2012-10-30 21:35 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-29 22:12 possibly memory leak in alsa-lib Ivan Sorokin
2012-10-30 10:48 ` Jaroslav Kysela
2012-10-30 21:36 ` Ivan Sorokin [this message]
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=50904849.5030101@gmail.com \
--to=vanyacpp@gmail.com \
--cc=alsa-devel@alsa-project.org \
--cc=perex@perex.cz \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.