Alsa-Devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Lee Revell <rlrevell@joe-job.com>
To: Takashi Iwai <tiwai@suse.de>
Cc: alsa-devel <alsa-devel@lists.sourceforge.net>
Subject: Re: memory leaks?
Date: Tue, 29 Mar 2005 16:31:56 -0500	[thread overview]
Message-ID: <1112131916.5386.6.camel@mindpipe> (raw)
In-Reply-To: <1112127843.5141.12.camel@mindpipe>

On Tue, 2005-03-29 at 15:24 -0500, Lee Revell wrote:
> On Tue, 2005-03-29 at 14:27 +0200, Takashi Iwai wrote:
> > Yes.  Could you trace the corresponding addresses?
> > (just checking /proc/kallsyms before unloading would help, too).
> 
> How exactly would I trace those addresses?
> 
> Anyway, it looks to me that the leak is in snd_seq_midi.  Here is the
> most recent output.  The first one I'm not sure about, the second seems
> to be in snd_seq_midisynth_register_port.

I might have found it.  The info structure allocated in
snd_seq_midisynth_register_port does not seem to be freed in
snd_seq_midisynth_unregister_port, except on the error paths.

Lee



-------------------------------------------------------
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

  reply	other threads:[~2005-03-29 21:31 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
2005-03-29 20:24   ` Lee Revell
2005-03-29 21:31     ` Lee Revell [this message]
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=1112131916.5386.6.camel@mindpipe \
    --to=rlrevell@joe-job.com \
    --cc=alsa-devel@lists.sourceforge.net \
    --cc=tiwai@suse.de \
    /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