search

omkar176 / xuggle

Automatically exported from code.google.com/p/xuggle
0 stars 0 forks source link

Crash while seeking in an m4v #241

Open GoogleCodeExporter opened 8 years ago

GoogleCodeExporter commented 8 years ago 
Attempting to seek using the new seek API causes a crash consistently.  I'm 
testing with an m4v file on Mac OS X 
10.6.3 and the latest stable Xuggler.  Steps to reproduce:

1. Open m4v file with an IMediaReader
2. Let it play normally for a few seconds (6.3 in this case, timestamp 6333333)
3. Try and seek forward by 0.5 s with
mediaReader.getContainer().seekKeyFrame(0, 5833333,
                6833333, 7833333, 0)
4. The seek returns succesfully but on the next call to 
mediaReader.readPacket() it will blow up.

Original issue reported on code.google.com by kareem.s...@gmail.com on 14 May 2010 at 3:52

GoogleCodeExporter commented 8 years ago 
Log from the console:

2010-05-14 11:39:14,360 [XuggleDecoder] TRACE com.xuggle.ferry.NativeLogger - 
Native code asked for logger: org.ffmpeg
2010-05-14 11:39:14,360 [XuggleDecoder] TRACE com.xuggle.ferry.NativeLogger - 
Native code asked for logger: org.ffmpeg
2010-05-14 11:39:14,360 [XuggleDecoder] TRACE com.xuggle.ferry.NativeLogger - 
log level: 0, msg: [NULL @ 0x10092ae00] hmm, seems the headers are not 
complete, 
trying to guess time_increment_bits
2010-05-14 11:39:14,360 [XuggleDecoder] TRACE com.xuggle.ferry.NativeLogger - 
log level: 0, msg: [NULL @ 0x10092ae00] hmm, seems the headers are not 
complete, 
trying to guess time_increment_bits
2010-05-14 11:39:14,360 [XuggleDecoder] ERROR org.ffmpeg - [NULL @ 0x10092ae00] 
hmm, seems the headers are not complete, trying to guess time_increment_bits
2010-05-14 11:39:14,360 [XuggleDecoder] ERROR org.ffmpeg - [NULL @ 0x10092ae00] 
hmm, seems the headers are not complete, trying to guess time_increment_bits
2010-05-14 11:39:14,361 [XuggleDecoder] TRACE com.xuggle.ferry.NativeLogger - 
log level: 0, msg: [NULL @ 0x10092ae00] my guess is 4 bits ;)
2010-05-14 11:39:14,361 [XuggleDecoder] TRACE com.xuggle.ferry.NativeLogger - 
log level: 0, msg: [NULL @ 0x10092ae00] my guess is 4 bits ;)
2010-05-14 11:39:14,361 [XuggleDecoder] ERROR org.ffmpeg - [NULL @ 0x10092ae00] 
my guess is 4 bits ;)
2010-05-14 11:39:14,361 [XuggleDecoder] ERROR org.ffmpeg - [NULL @ 0x10092ae00] 
my guess is 4 bits ;)
2010-05-14 11:39:14,361 [XuggleDecoder] TRACE com.xuggle.ferry.NativeLogger - 
log level: 0, msg: [NULL @ 0x10092ae00] looks like this file was encoded with 
(divx4/(old)xvid/opendivx) -> forcing low_delay flag
2010-05-14 11:39:14,361 [XuggleDecoder] TRACE com.xuggle.ferry.NativeLogger - 
log level: 0, msg: [NULL @ 0x10092ae00] looks like this file was encoded with 
(divx4/(old)xvid/opendivx) -> forcing low_delay flag
2010-05-14 11:39:14,361 [XuggleDecoder] ERROR org.ffmpeg - [NULL @ 0x10092ae00] 
looks like this file was encoded with (divx4/(old)xvid/opendivx) -> forcing 
low_delay 
flag
2010-05-14 11:39:14,361 [XuggleDecoder] ERROR org.ffmpeg - [NULL @ 0x10092ae00] 
looks like this file was encoded with (divx4/(old)xvid/opendivx) -> forcing 
low_delay 
flag
Invalid memory access of location 0x38 rip=0x12820d511

Original comment by kareem.s...@gmail.com on 14 May 2010 at 3:53

GoogleCodeExporter commented 8 years ago 
Attached is the crash log from Mac OS X.

Original comment by kareem.s...@gmail.com on 14 May 2010 at 3:54

Attachments: