From mboxrd@z Thu Jan 1 00:00:00 1970 From: Lee Revell Subject: Re: memory leaks Date: Wed, 06 Jul 2005 13:34:36 -0400 Message-ID: <1120671276.10268.6.camel@mindpipe> References: Mime-Version: 1.0 Content-Type: text/plain Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: Sender: alsa-devel-admin@lists.sourceforge.net Errors-To: alsa-devel-admin@lists.sourceforge.net List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , List-Archive: To: Clemens Ladisch Cc: alsa-devel List-Id: alsa-devel@alsa-project.org On Wed, 2005-07-06 at 10:06 +0200, Clemens Ladisch wrote: > Lee Revell wrote: > > WHen reloading ALSA modules I got this message: > > 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. > > These functions don't directly allocate memory, the leak is probably > in some driver function. What hwdep device is this? snd_emu10k1_synth I think. 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