[Ffmpeg-devel] segfault in ff_mpeg1_find_frame_end()

Stefan Lucke stefan
Sat May 14 01:13:02 CEST 2005

On Samstag, 14. Mai 2005 00:17, M?ns Rullg?rd wrote:
> Stefan Lucke <stefan at lucke.in-berlin.de> writes:

> > I just made some progress. At the beginning of function MPV_common_end()
> > there are av_freep() for the parser buffer and parser buffer_size
> > is set to 0. But I think pointer into the parses buffer are still
> > present. So I commented out these two lines and even with av_read_packet()
> > I get __no__ crash.
> >
> > I run valgrind with the modified code and there are no new leaks compared
> > to run without my modification.
> What does a valgrind say when it does crash?  That's what's
> interesting.

I certenly cannot run valgrind with a realtime video decoding software
on my box. For that it is to slow and as softdevice tries up to sync
the video to real time, it is not not guaranteed the the same code gets
executed and/or the frames are decoded (they are skipped).

But I tried it. I used a statically linked ffmpeg libs. It's a script
in which I inserted the following line:
--- about that time crashing stream started playback ---

This time there was no segfault but there are some messages
when there is the 4:3 16:9 switch. the plain 4:3 part was without.
Hopefully we can get some hints for the segault.
Thanks for your patience.

Stefan Lucke
-------------- next part --------------
A non-text attachment was scrubbed...
Name: valgrind.static.log.bz2
Type: application/x-bzip2
Size: 5139 bytes
Desc: not available
URL: <http://lists.mplayerhq.hu/pipermail/ffmpeg-devel/attachments/20050514/40933bd3/attachment.bin>

More information about the ffmpeg-devel mailing list