From: Lee Revell <rlrevell@joe-job.com>
To: alsa-devel <alsa-devel@lists.sourceforge.net>
Subject: memory leaks
Date: Tue, 05 Jul 2005 22:52:27 -0400 [thread overview]
Message-ID: <1120618347.5803.3.camel@mindpipe> (raw)
WHen reloading ALSA modules I got this message:
ALSA sound/core/memory.c:71: Not freed snd_alloc_kmalloc = 1728
ALSA sound/core/memory.c:80: kmalloc(164) from dc8506f9 not freed
ALSA sound/core/memory.c:80: kmalloc(268) from dc850606 not freed
ALSA sound/core/memory.c:80: kmalloc(164) from dc8506f9 not freed
ALSA sound/core/memory.c:80: kmalloc(268) from dc850606 not freed
ALSA sound/core/memory.c:80: kmalloc(164) from dc8506f9 not freed
ALSA sound/core/memory.c:80: kmalloc(268) from dc850606 not freed
ALSA sound/core/memory.c:80: kmalloc(164) from dc8506f9 not freed
ALSA sound/core/memory.c:80: kmalloc(268) from dc850606 not freed
These are the closest symbols:
dc850590 t snd_hwdep_ioctl [snd_hwdep]
dc850630 t snd_hwdep_mmap [snd_hwdep]
dc850660 t snd_hwdep_control_ioctl [snd_hwdep]
AFAICT this means the leaks are in snd_hwdep_ioctl and control_ioctl.
Lee
-------------------------------------------------------
SF.Net email is sponsored by: Discover Easy Linux Migration Strategies
from IBM. Find simple to follow Roadmaps, straightforward articles,
informative Webcasts and more! Get everything you need to get up to
speed, fast. http://ads.osdn.com/?ad_id=7477&alloc_id=16492&op=click
next reply other threads:[~2005-07-06 2:52 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-07-06 2:52 Lee Revell [this message]
2005-07-06 8:06 ` memory leaks Clemens Ladisch
2005-07-06 17:34 ` Lee Revell
-- strict thread matches above, loose matches on Subject: below --
2005-09-30 2:49 [ 1/9 ] [ SEPOL ] Eliminate struct pointer typedefs Ivan Gyurdiev
2005-09-30 3:29 ` Memory leaks Ivan Gyurdiev
2005-09-30 6:01 ` Ivan Gyurdiev
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=1120618347.5803.3.camel@mindpipe \
--to=rlrevell@joe-job.com \
--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.