similar to: Ices memory leak?

Is anyone else experiencing what seems to be a memory leak with Ices? I can have icecast up and running with WinAmp streaming to it from my '98 box for days at a time with no problem. As soon as I start Ices I'll launch top to watch and my free mem starts dropping -fast-. Starting from about 160MB free, in 4-5 hours I have 2MB free with Ices crashed and the memory unrecovered which sends

On Monday, 10 September 2001 at 12:45, Jason Mansfield wrote: > Is anyone else experiencing what seems to be a memory > leak with Ices? I can have icecast up and running with > WinAmp streaming to it from my '98 box for days at a > time with no problem. As soon as I start Ices I'll > launch top to watch and my free mem starts dropping > -fast-. Starting from about 160MB

Great. If you have some pointers with further explanations, that'd be great, because lately I've been wondering why 256 MB fills up all the way to the point my desktop system slows to a crawl. Someone seriously messed with the 2.4.x memory handling. It's probably caching and mmap'ing lots of stuff but I want it to pipe DOWN ! o any pointers are appreciated. Especially on the

I posted a while back about having trouble with ices 0.2.2 being able to re-encode VBR mp3s, and the response was that ices 0.2.2 did not reencode VBR mp3s. Are there any plans to include such support in future ices versions? If so, any ideas as to when such versions would become available? Thanks, -- "Shall life renew these bodies of a truth? Steve Chadsey All death will

>> stable Ices 0.2.2 is? Are there enough fixes in it that it's worth using it? > > I wouldn't run anything but the current code. Brendan is pretty > good about fixing bugs if you run into any. A few people have been > using 0.2.2 for a while. Does ices 0.2.2 show the album name in the meta information, or just the artist & songname? Thanks, Mark --- >8 ----

I notice two versions on the Web site, 0.2.2 being shown as developmental. I'm building a new server that will run Icecast 1.3.11 and I'm wondering how stable Ices 0.2.2 is? Are there enough fixes in it that it's worth using it? Thanks, Hunter --- >8 ---- List archives: http://www.xiph.org/archives/ icecast project homepage: http://www.icecast.org/ To unsubscribe from this list,

Any help would be appreciated, not sure why this isn't compiling: Redhat 7.2 [root@jasmine ices-0.2.2]# ./configure --with-lame loading cache ./config.cache Building ices 0.2.2... checking for a BSD compatible install... (cached) /usr/bin/install -c checking whether build environment is sane... yes checking whether make sets ${MAKE}... (cached) yes checking for working aclocal... found

I recently upgraded ices from 0.1.0 to 0.2.2. I have found that it is not reencoding my mp3 stream, even though I have it configured to. This is on a RedHat linux 7.0 system, kernel 2.4.11 ices build commands: ./configure --with-perl --with-lame \ --with-lame-includes=/usr/local/src/lame-3.89/include \ --with-lame-libraries=/usr/local/src/lame-3.89/libmp3lame/.libs gmake

Also sprach Michael Smith: > > >Ok. I'm using shout and not ices (I couldn't get it to compile; I'm > >using FreeBSD and can't code C worth a damn), so the second approach > >will not work. But I can write a parsing script (I had'n thought of > >the cue file), so I'll be trying that. > > Please don't use shout. It's buggy,

Moritz Grimm wrote: > > Bolt Thrower wrote: > > > >From my ices.conf: > > <Bitrate>64</Bitrate> > > > My mp3s are encoded with the following command: > > /usr/local/src/lame3.86/lame -S -V 1 -b 128 -h -m j \ > > --tt "title" --ta "artist" --tl "album" \ > > --ty "year"

First off, I managed to build iceS 0.2.2 with Python 2.1, though I had to add -lutil to the $LIBS definition whilst ./configure'ing. Otherwise, configure won't find Py_Initialize Secondly - multiple streams I've added a second "stream" definition to my ices.conf, and both streams show up as sources for icecast, (http://blah.com:8000/list.cgi), though when i try to connect

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 I run FreeBSD-4.5-STABLE, along with icecast 1.3.12, and I've been having two problems with ices 0.2.2. 1) When I give ices an empty playlist file and tell it to randomize, I get a segfault every time. When I give it the same playlist with Randomize set to 0, it tells me that the playlist is empty instead of crashing. 2) ices can't

hello, i'm starting/stopping icecast (1.3.11) & ices (0.2.2) from a web interface. fine so far, but now i see strange things: both ices & icecast, once started , (ices -B ... , icecast -b ...), both processes and their childs are listening also to port 80, besides their normal operation. i've found out because apache didn't restart (Address already in use: make_sock: could

Okay, I did this right months ago, but somehow lost the recipe. I have libxml and libxml2 installed: [root@atisha ices-0.2.2]# ls /usr/local/lib libshout.a libxml2.a libxml.a pkgconfig libshout.la libxml2.la libxml.la xml2Conf.sh libshout.so libxml2.so libxml.so xmlConf.sh libshout.so.1 libxml2.so.2 libxml.so.1

hiya. i'm using ices 0.2.2 with icecast 1.3.10 and otto 1.0 (a web/db playlist mgmt tool). overall, i'm very pleased with the setup, but i'm having a few problems. 1) whenever otto plays a track (by exec'ing ices), that same track keeps playing over and over. i have to direct otto to kill the track (and the ices process) in order to get it to play the next track. i notice this

Hi, I'm having difficulty getting ices 0.2.2 to see my lame install and my perl install. The lame libraries (v3.91) are installed in: /usr/local/lib/ with the header file at: /usr/local/include/lame/lame.h, but when I run: ./configure --with-lame --with-lame-includes=/usr/local/include/lame/ --with-lame-libraries=/usr/local/ it says it can't find the lame libraries. ldconfig seems

> > The response I got at the time from Brendan Cully: > > He's the man in the know, so what he says is probably true. Maybe if > you asked him nicely he'd cook up a small patch for you :) > > jack. > I worked out a patch for ices-0.2.2 that forces ices to *always* re-encode the stream if Reencode is enabled: --- CUT HERE --- --- src/stream.c.orig Thu Jul 26

Hey Harvey -- all you need to do is to add -lutil to the $LIBS list around line 3968 of "configure" LIBS="-l$lib -lm -ldl $LIBS" becomes LIBS="-l$lib -lm -ldl -lutil $LIBS" hould solve yer problems. also, around line 3957, in the 'for lib in python python2.0 python1.6, etc, you may want to add python2.1 (if you have 2.1 installed, else it may have trouble

I'm having more than a bit of trouble getting Ices installed with Lame support (I've been running it without Lame support for a couple of months now without much trouble. But with Lame it's not compiling. It's recognizing the libraries in the ./configure stage. gmake ends with these errors: gmake[3]: Entering directory `/usr/local/src/ices-0.2.2/src' gcc -DHAVE_CONFIG_H -I.

I have serious problems to compile IceS on a debian (woody), kernel 2.4.18. I have to say the configure script does not find anything... - I installed libshout and libshout-dev downloaded drom the icecast site. I have shout.h : 0:33 root@radiopi2 /usr/include/shout# ls shout.h Yet configure gives me this : ~/sources/ices-0.2.2% ./configure --with-libshout=/usr/include checking for