vlc error INPUT_MAX_ALLOCATION reached?
Christophe Massiot
massiot at via.ecp.fr
Fri Mar 22 00:53:23 CET 2002
À (At) 14:22 +0100 21/03/2002, Bill Eldridge écrivait (wrote) :
>Christophe Massiot wrote:
>>
>> (At) 16:36 +0100 20/03/2002, Bill Eldridge écrivait (wrote) :
>> >[root at rfa01 bill]# vlc --noaudio http://localhost:8090/test1.vob
>> >VideoLAN Client - version 0.2.92-dev_2002-03-20 Ourumov - (c) 1996-2002
>> >VideoLAN
>> >INPUT_MAX_ALLOCATION reached (20971637)
>> >
>> >What does it mean?
>>
>> I have been told the HTTP input seems to be malfunctioning since
>> input III. I will have a look at this, as soon as I have five
>> minutes...
>
>Yes, this seems to be true
It works perfectly for me with Dolby_Broadway.vob. For people who
have problems with it, please find a reproducible situation...
> - it's now crashing
>ffserver when I try to connect, and I'm not
>sure if the error is because ffserver has already
>died, or if there's some condition in vlc here
>that makes it mess up and then send something
>awful to ffserver.
As far as I'm concerned, it's not "good behaviour" for a program to
crash when it gets unexpected queries :-p. That being said, I suspect
the problem might be with the Range: header we are now using for
seeking. Remove the :
"Range: bytes=%lld-\r\n"
line in plugins/access/http.c and tell me if it helps.
--
Christophe Massiot.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mailman.videolan.org/pipermail/vlc/attachments/20020322/bb3f16c3/attachment.html>
More information about the vlc
mailing list