From owner-freebsd-questions Mon Aug 23 10:29:26 1999 Delivered-To: freebsd-questions@freebsd.org Received: from shell2.la.best.com (shell2.la.best.com [209.24.216.141]) by hub.freebsd.org (Postfix) with ESMTP id 9295F14F0E; Mon, 23 Aug 1999 10:29:09 -0700 (PDT) (envelope-from nugundam@shell2.la.best.com) Received: from localhost (nugundam@localhost) by shell2.la.best.com (8.9.3/8.9.2/best.sh) with ESMTP id KAA24206; Mon, 23 Aug 1999 10:27:22 -0700 (PDT) Date: Mon, 23 Aug 1999 10:27:22 -0700 (PDT) From: Joseph Lee To: freebsd-multimedia@freebsd.org, freebsd-questions@freebsd.org Subject: mpg123 leaking memory? Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I'm running on a recent 3.2-stable setup with 128MB ram and 150M swap, and the recent mpg123 from ports through the pcm0 kernel driver, with the gqmpeg player. I've been watching the RES size of the playing mpg123 process as it plays a MP3, and the active memory usage increase as it plays a mp3. It never seems to free this memory nor does any of the memory goes back into the inactive pool after the mp3 is done and moves on to the next (whether mpg123 is run from gqmpeg or commandline). On a usual overnight run without mpg123, I should be somewhere around 80MB used in Windowmaker and no swap used. After a overnight run with mpg123, I'm seeing 22M of swap used and increasing. Is this normal behavior of the memory architecture? I haven't been awake when swap usage gets been maxed out, but the system does reboot because I think no swap left so it panics. So, is mpg123 leaking memory? Playing CDs through ascd has no such problems. Joseph To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message