From: Takashi Iwai <tiwai@suse.de>
To: Lee Revell <rlrevell@joe-job.com>
Cc: alsa-devel <alsa-devel@lists.sourceforge.net>
Subject: Re: memory leaks?
Date: Tue, 29 Mar 2005 14:27:59 +0200 [thread overview]
Message-ID: <s5hpsxiiqls.wl@alsa2.suse.de> (raw)
In-Reply-To: <1111896886.2408.1.camel@mindpipe>
At Sat, 26 Mar 2005 23:14:46 -0500,
Lee Revell wrote:
>
> I recently started getting these messages every time I relaod my ALSA modules:
>
> usbcore: registered new driver snd-usb-audio
> usbcore: deregistering driver snd-usb-audio
> ALSA /home/rlrevell/cvs/alsa/alsa-driver/usb/usbmidi.c:178: urb status -108
> ALSA /home/rlrevell/cvs/alsa/alsa-driver/usb/usbmidi.c:163: usb_submit_urb: -90
> ALSA /home/rlrevell/cvs/alsa/alsa-driver/alsa-kernel/core/memory.c:71: Not freed snd_alloc_kmalloc = 864
> ALSA /home/rlrevell/cvs/alsa/alsa-driver/alsa-kernel/core/memory.c:80: kmalloc(164) from e0979806 not freed
> ALSA /home/rlrevell/cvs/alsa/alsa-driver/alsa-kernel/core/memory.c:80: kmalloc(268) from e09796fe not freed
> ALSA /home/rlrevell/cvs/alsa/alsa-driver/alsa-kernel/core/memory.c:80: kmalloc(164) from e0979806 not freed
> ALSA /home/rlrevell/cvs/alsa/alsa-driver/alsa-kernel/core/memory.c:80: kmalloc(268) from e09796fe not freed
> PCI: Found IRQ 7 for device 0000:00:0f.0
> ALSA /home/rlrevell/cvs/alsa/alsa-driver/alsa-kernel/core/memory.c:71: Not freed snd_alloc_kmalloc = 432
> ALSA /home/rlrevell/cvs/alsa/alsa-driver/alsa-kernel/core/memory.c:80: kmalloc(164) from e098a806 not freed
> ALSA /home/rlrevell/cvs/alsa/alsa-driver/alsa-kernel/core/memory.c:80: kmalloc(268) from e098a6fe not freed
> ( ksoftirqd/0-2 |#0): new 48 us maximum-latency wakeup.
> PCI: Found IRQ 7 for device 0000:00:0f.0
> usb 2-2: USB disconnect, address 3
> ( IRQ 12-664 |#0): new 51 us maximum-latency wakeup.
> ( IRQ 10-2804 |#0): new 70 us maximum-latency wakeup.
> ALSA /home/rlrevell/cvs/alsa/alsa-driver/alsa-kernel/core/memory.c:71: Not freed snd_alloc_kmalloc = 432
> ALSA /home/rlrevell/cvs/alsa/alsa-driver/alsa-kernel/core/memory.c:80: kmalloc(164) from e08b4806 not freed
> ALSA /home/rlrevell/cvs/alsa/alsa-driver/alsa-kernel/core/memory.c:80: kmalloc(268) from e08b46fe not freed
> PCI: Found IRQ 7 for device 0000:00:0f.0
> ( ksoftirqd/0-2 |#0): new 85 us maximum-latency wakeup.
> ( ksoftirqd/0-2 |#0): new 90 us maximum-latency wakeup.
> ( IRQ 11-691 |#0): new 100 us maximum-latency wakeup.
>
> Does this indicate a memory leak in ALSA?
Yes. Could you trace the corresponding addresses?
(just checking /proc/kallsyms before unloading would help, too).
Takashi
-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
next prev parent reply other threads:[~2005-03-29 12:27 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-27 4:14 memory leaks? Lee Revell
2005-03-29 12:27 ` Takashi Iwai [this message]
2005-03-29 20:24 ` Lee Revell
2005-03-29 21:31 ` Lee Revell
2005-03-30 12:08 ` Takashi Iwai
2005-03-30 12:18 ` Takashi Iwai
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=s5hpsxiiqls.wl@alsa2.suse.de \
--to=tiwai@suse.de \
--cc=alsa-devel@lists.sourceforge.net \
--cc=rlrevell@joe-job.com \
/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.