Hi Ross,

Searching in the mailing list, I saw some discussion about the BANK_SIZE, the 
last one I found seems to say that it is no more needed at least for H264 
parsing.

I reach this limit parsing an MKV file with an H264 stream.
It's annoying that parsing a file makes abort the process with the following 
backtrace :
#2  0x00000000008c7b61 in UsageEnvironment::internalError (this=0x138fd60) at 
UsageEnvironment.cpp:46
#3  0x00000000008bc809 in StreamParser::ensureValidBytes1 (this=0x13e0530, 
numBytesNeeded=289877) at StreamParser.cpp:151
#4  0x00000000008bf1c1 in StreamParser::ensureValidBytes (this=0x13e0530, 
numBytesNeeded=289877) at StreamParser.hh:118
#5  0x00000000008bf12a in StreamParser::skipBytes (this=0x13e0530, 
numBytes=289877) at StreamParser.hh:92
#6  0x00000000008b4760 in MatroskaFileParser::parseBlock (this=0x13e0530) at 
MatroskaFileParser.cpp:769
#7  0x00000000008b3179 in MatroskaFileParser::parse (this=0x13e0530) at 
MatroskaFileParser.cpp:155
#8  0x00000000008b3006 in MatroskaFileParser::continueParsing (this=0x13e0530) 
at MatroskaFileParser.cpp:96
...

Could be possible in a future release to add a way to customize this value and  
return a parsing error instead of aborting ?
I guess it could be possible to customize the buffer size setting a value in 
the UsageEnvironement, and return a parsing error when the buffer overflow ?

Best Regards,

            Michel.
_______________________________________________
live-devel mailing list
live-devel@lists.live555.com
http://lists.live555.com/mailman/listinfo/live-devel

Reply via email to