Justin,
I'm not a linux guy, or a that well versed on ICES, but, I went thru the
code (stream.c) and just kinda nosed around the broadcast part. When we
look at distros that this uses, it may be the correct version of the
package, but it might actually be a supporting package, like curl or
something like that. If you look at the code attached below, it shows there
might be some kind of memory leak that needs to be taken care of. This is
in the sdsc stream description, which if I'm right, uses shout. (#include
<shout/shout.h>)
Maybe the error you're finding is because you have special chars, or bad
chars, and the version of shout you're using isn't right. When I look
at
the code below (sorry, can't read machine language to guess what you put
into pastebin). Have you taken a chance to set your logging to a high level
to see what the error log says? That may shed some light as to what the
error could be.
But if you go thru the log and check out the errors, and then go back and
look at the stream.c file that's included in the source, you could search on
the error code, find where it's blowing up, and then try to figure out what
library it's using when it does. There may be a different version of that
library for each different processor.
if(encoding)
{
if(inmod->metadata_update)
inmod->metadata_update(inmod->internal, &sdsc->vc);
sdsc->enc = encode_initialise(stream->channels,
stream->samplerate,
stream->managed, stream->min_br, stream->nom_br,
stream->max_br,
stream->quality, &sdsc->vc);
if(!sdsc->enc) {
LOG_ERROR0("Failed to configure encoder");
stream->died = 1;
shout_free (sdsc->shout);
sdsc->shout = NULL;
return NULL; /* FIXME: probably leaking some memory here */
}
sdsc->enc->max_samples_ppage =
sdsc->stream->max_samples_ppage;
}
-----Original Message-----
From: icecast-bounces at xiph.org [mailto:icecast-bounces at xiph.org] On Behalf
Of icecast-request at xiph.org
Sent: Monday, January 09, 2012 2:00 PM
To: icecast at xiph.org
Subject: Icecast Digest, Vol 92, Issue 2
Send Icecast mailing list submissions to
icecast at xiph.org
To subscribe or unsubscribe via the World Wide Web, visit
http://lists.xiph.org/mailman/listinfo/icecast
or, via email, send a message with subject or body 'help' to
icecast-request at xiph.org
You can reach the person managing the list at
icecast-owner at xiph.org
When replying, please edit your Subject line so it is more specific than
"Re: Contents of Icecast digest..."
Today's Topics:
1. EZSTREAM: Playlist Automation Script for Windows (Doc Nasty)
----------------------------------------------------------------------
Message: 1
Date: Mon, 9 Jan 2012 01:34:12 -0600
From: "Doc Nasty" <doc at krushradio.com>
Subject: [Icecast] EZSTREAM: Playlist Automation Script for Windows
To: <icecast at xiph.org>
Message-ID: <000901cccea1$15d1a8a0$4174f9e0$@krushradio.com>
Content-Type: text/plain; charset="us-ascii"
Hey All,
Happy New Year! I have a question regarding EZStream for Windows. I saw in
one of the examples, I could use a script, such as a playlist.pl. Is it
possible to use a custom .exe file, or a vbs/wsh script instead?
Thanks,
Doc
-----Original Message-----
From: icecast-bounces at xiph.org [mailto:icecast-bounces at xiph.org] On Behalf
Of icecast-request at xiph.org
Sent: Tuesday, January 03, 2012 2:00 PM
To: icecast at xiph.org
Subject: Icecast Digest, Vol 92, Issue 1
Send Icecast mailing list submissions to
icecast at xiph.org
To subscribe or unsubscribe via the World Wide Web, visit
http://lists.xiph.org/mailman/listinfo/icecast
or, via email, send a message with subject or body 'help' to
icecast-request at xiph.org
You can reach the person managing the list at
icecast-owner at xiph.org
When replying, please edit your Subject line so it is more specific than
"Re: Contents of Icecast digest..."
Today's Topics:
1. *Bump* ices2 memory leak on Debian/ARM (The Darkener)
----------------------------------------------------------------------
Message: 1
Date: Mon, 02 Jan 2012 13:21:27 -0800
From: The Darkener <thedarkener at logicalnetworking.net>
Subject: [Icecast] *Bump* ices2 memory leak on Debian/ARM
To: icecast at xiph.org
Message-ID: <4F021FD7.8040002 at logicalnetworking.net>
Content-Type: text/plain; charset=ISO-8859-1
Hi all,
I was really hoping to get a bit of help from this. I've since gone to
ezstream to try and accomplish the same goal, but ices2 is so simple to use
I would really like to stay with that instead.
Can anyone help me debug this memory leak? I can't use valgrind to try and
debug because it throws an "Illegal Instruction" whenever I try to run
it.
:(
Happy New Year!
Jordan
On 12/15/2011 05:30 PM, TheDarkener wrote:> Hi all.. I'm having a memory leak issue with Ices2 (using package
> 2.0.1-8 from Debian stable on arm platform)..
>
> I've tried turning off metadata, modifying samplerate, and some other
> misc. things that haven't helped. Eventually, during a stream, ices2
> will invoke oom-killer and bring the whole system down. It eats about
> 0.05MB/Sec of memory, so it takes a while, but this plug has 512mb, so
> about 2 hours into a stream, it will die.
>
> Any ideas? I can't seem to find anything online, especially regarding
> my arch. Nothing really shows up in the logs, even though I have ices
> set to 4 (debug) log output. I have a small portion of the strace
> output when running ices2... it keeps going, incrementing at the
'brk'
calls...> here: http://pastebin.com/5UHpM49s
>
> I have a system with identical configuration, only i386-based (an ASUS
> laptop). This system, with the same packages (but different arch)
> doesn't experience the memory leak.
>
> Any help or questions for me would be greatly appreciated :)
>
>
> Cheers,
> Jordan
>
>
--
Jordan (PGP: 0xDA470FF8)
------------------------------
_______________________________________________
Icecast mailing list
Icecast at xiph.org
http://lists.xiph.org/mailman/listinfo/icecast
End of Icecast Digest, Vol 92, Issue 1
**************************************
------------------------------
_______________________________________________
Icecast mailing list
Icecast at xiph.org
http://lists.xiph.org/mailman/listinfo/icecast
End of Icecast Digest, Vol 92, Issue 2
**************************************
Keith Roberts
2012-Jan-10 15:43 UTC
[Icecast] ices2 memory leak on Debian/ARM (The Darkener)
On Mon, 9 Jan 2012, Doc Nasty wrote:> To: icecast at xiph.org > From: Doc Nasty <doc at krushradio.com> > Subject: Re: [Icecast] ices2 memory leak on Debian/ARM (The Darkener) > > Justin, > > I'm not a linux guy, or a that well versed on ICES, but, I went thru the > code (stream.c) and just kinda nosed around the broadcast part. When we > look at distros that this uses, it may be the correct version of the > package, but it might actually be a supporting package, like curl or > something like that. If you look at the code attached below, it shows there > might be some kind of memory leak that needs to be taken care of. This is > in the sdsc stream description, which if I'm right, uses shout. (#include > <shout/shout.h>)There's a Linux memory profiler called: "Valgrind" is a multipurpose code profiling and memory debugging tool for Linux when on the x86 and, as of version 3, AMD64, architectures. It allows you to run your program in Valgrind's own environment that monitors memory usage such as calls to malloc and free (or new and delete in C++). If you use uninitialized memory, write off the end of an array, or forget to free a pointer, Valgrind can detect it. Since these are particularly common problems, this tutorial will focus mainly on using Valgrind to find these types of simple memory problems, though Valgrind is a tool that can do a lot more. that might help you out. I've used it to find programs running under Linux with bad memory management. For other memory leakage tools, just Google for something like: memory leak detection tools Kind Regards, Keith Roberts ----------------------------------------------------------- Websites: http://www.karsites.net http://www.php-debuggers.net http://www.raised-from-the-dead.org.uk All email addresses are challenge-response protected with TMDA [http://tmda.net] -----------------------------------------------------------
TheDarkener
2012-Jan-10 23:02 UTC
[Icecast] ices2 memory leak on Debian/ARM (The Darkener)
Hi Keith, As I explained before, Valgrind won't run in my arch. I'll Google for some other memory leak detection tools, however. Thank you for your input...I look forward to helping fix this bug! - Jordan On 01/10/2012 07:43 AM, Keith Roberts wrote:> *snip* > There's a Linux memory profiler called: > > "Valgrind" is a multipurpose code profiling and memory > debugging tool for Linux when on the x86 and, as of version > 3, AMD64, architectures. It allows you to run your program > in Valgrind's own environment that monitors memory usage > such as calls to malloc and free (or new and delete in C++). > If you use uninitialized memory, write off the end of an > array, or forget to free a pointer, Valgrind can detect it. > Since these are particularly common problems, this tutorial > will focus mainly on using Valgrind to find these types of > simple memory problems, though Valgrind is a tool that can > do a lot more. > > that might help you out. I've used it to find programs > running under Linux with bad memory management. > > For other memory leakage tools, just Google for something > like: memory leak detection tools > > Kind Regards, > > Keith Roberts > > ----------------------------------------------------------- > Websites: > http://www.karsites.net > http://www.php-debuggers.net > http://www.raised-from-the-dead.org.uk > > All email addresses are challenge-response protected with > TMDA [http://tmda.net] > ----------------------------------------------------------- > _______________________________________________ > Icecast mailing list > Icecast at xiph.org > http://lists.xiph.org/mailman/listinfo/icecast-- Jordan (PGP: 0xDA470FF8)