Hi! 2016-11-07 1:32 GMT+01:00 Moritz Barsnick <[email protected]>: > On Mon, Nov 07, 2016 at 00:26:03 +0100, Carl Eugen Hoyos wrote: >> Not reproducible with file output? > > No. If I replace either of the rtmp:// with "file:file1", I see no > issues.
Ok. >> > list". None of this occurs - never! - with gdb attached. :-( >> >> Use valgrind instead, you may have to force a very (!) small >> resolution. > > I'm really no good at valgrind. I needed to recompile > because my ancient version saw illegal instructions. Try (without valgrind) with -cpuflags 0 If it still crashes, you can use -cpuflags 0 with valgrind (which will avoid the illegal instruction). No valgrind update from your distribution? > D'uh. I assume, first of all, > memcheck (default) is the tool to use. The only option I see > to change resolution is "--leak-resolution=low|med|high". > But whatever I do, I see no crashes running under valgrind. No, I meant you have to reduce the resolution of your ffmpeg encode above with -s qcif or similar because valgrind is more than a magnitude slower than your cpu. Carl Eugen _______________________________________________ ffmpeg-user mailing list [email protected] http://ffmpeg.org/mailman/listinfo/ffmpeg-user To unsubscribe, visit link above, or email [email protected] with subject "unsubscribe".
