[icecast] YP submission / cURL issue. (icecast 2.0.1 / gentoo)
cpickert at t3inc.us
cpickert at t3inc.us
Tue May 25 23:19:56 PDT 2004
I've yet to assemble a valid crash-procedure to consistently re-produce the
issue. AFAIK, whats causing it is possibly CPU-utilization issues with my
chaining of processing/DSP, what do y'all think?! -- My encoder setup:
`[DSP] -> SoundSolution (dynamic sonic enhancement)
`[Output] -> SqrSoft Crossfading (only ''REAL'' crossfader)
`[SqrSoft DSP Emul]` -> (Sqrsoft HAS to be 'output' and then MUX DSPs)
| 2x - Oddcast 2.0.13 -> Icecast
| 2x - " " -> Shoutcast
| 2x - " " -> Windows Media
`[GenPurp] -> DoSomething (generate HTML to 'net mapped' web-server drive)
<p><p>I've got a total of six encoders and all the others. On a
song-transision / the
cross-fader will drive CPU dangerously high and I'm wondering if
there's a loss
of avail CPU time, will OddCast possibly choke/stall and then cause the
crash? This is where I'd guess the issue of where the crash is. It's almost
impossible to guess when it'll crash so I can't totally validate my
I know the encoder setup is not at all Icecast related, just the fact there's
all the processing that drives CPU to 100% as well as the way SqrSoft
crossfade with songs, the buffering mechanism is a little odd. Might want to
look at it if you're curious.
I don't see it happening on the (non-YP) Linux Icecast but it happens
in Win32 Icecast.
<p>Quoting Michael Smith <msmith at xiph.org>:
> On Wednesday 26 May 2004 14:24, cpickert at t3inc.us wrote:
>> I've been using the win32 icecast for ages now (which YP stuff works
>> great) but am wanting to move to the *nix[linux now via gentoo] variant as
>> I've been having troubles where icecast was crashing routinely and would
>> actually chain-crash my OddSock->Winamp on the encoder and if Winamp
>> crashed from a non-oddsock error, sometimes the icecast sever would crash
>> with it. Terrible stuff but I talked with Monty about it at SXSW and have
>> seen that 2.0.1 itself was released (by OddSock) to fix crashes related to
>> buffer overflows, but I've still experienced the issues.
> It really shouldn't do that. The 2.0.1 release was for a single
> overflow (that
> would never happen accidently - only through a deliberate attack), so I
> wouldn't expect that to help. However, if it's crashing, we'd really like to
> know about that - with enough details to reproduce (and hopefully fix).
> --- >8 ----
> List archives: http://www.xiph.org/archives/
> icecast project homepage: http://www.icecast.org/
> To unsubscribe from this list, send a message to 'icecast-request at xiph.org'
> containing only the word 'unsubscribe' in the body. No subject is needed.
> Unsubscribe messages sent to the list will be ignored/filtered.
<p>--- >8 ----
List archives: http://www.xiph.org/archives/
icecast project homepage: http://www.icecast.org/
To unsubscribe from this list, send a message to 'icecast-request at xiph.org'
containing only the word 'unsubscribe' in the body. No subject is needed.
Unsubscribe messages sent to the list will be ignored/filtered.
More information about the Icecast