All of lore.kernel.org
 help / color / mirror / Atom feed
From: James Courtier-Dutton <James@superbug.demon.co.uk>
To: "alsa-devel@lists.sourceforge.net" <alsa-devel@lists.sourceforge.net>
Subject: alsa memory leaks
Date: Tue, 15 Oct 2002 00:13:51 +1000	[thread overview]
Message-ID: <3DAAD11F.2050602@superbug.demon.co.uk> (raw)

Has anyone run a diagnosis tool like "memprof" on an application that 
uses alsa for audio out ?
I recently did this, and have found that alsa is a little leaky. It is 
mainly the mixer part of alsa.
Here is an example backtrace for the call to the malloc that is never 
freed even if the application exits.
Maybe I am just missing the alsa-lib api call to free up all the memory, 
but I thought I would mention it anyway.

There are lots of these: -
Leaked 0x8106038 (12 bytes)
        [0x400157b0]
        bag_add(): /alsa-lib/src/mixer/bag.c:47
        snd_mixer_elem_attach(): /alsa-lib/src/mixer/mixer.c:88
        simple_add1(): /alsa-lib/src/mixer/simple.c:966
        simple_event_add(): /alsa-lib/src/mixer/simple.c:1029
        simple_event(): /alsa-lib/src/mixer/simple.c:1062
        hctl_event_handler(): /alsa-lib/src/mixer/mixer.c:175
        snd_hctl_throw_event(): /alsa-lib/src/control/hcontrol.c:178
        snd_hctl_load(): /alsa-lib/src/control/hcontrol.c:567
        snd_mixer_load(): /alsa-lib/src/mixer/mixer.c:448
        ao_alsa_mixer_init(): /xine-lib/src/audio_out/audio_alsa_out.c:858

Cheers
James




-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf

                 reply	other threads:[~2002-10-14 14:13 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=3DAAD11F.2050602@superbug.demon.co.uk \
    --to=james@superbug.demon.co.uk \
    --cc=alsa-devel@lists.sourceforge.net \
    /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.