Re: [FFmpeg-trac] #10697(ffmpeg:new): Crash when using incompatible codec and hardware acceleration type

[FFmpeg]

#10697: Crash when using incompatible codec and hardware acceleration type
-+-
 Reporter:  iEvgeny  |Owner:  (none)
 Type:  defect   |   Status:  new
 Priority:  normal   |Component:  ffmpeg
  Version:  git-master   |   Resolution:
 Keywords:  ffmpeg   |   Blocked By:
  avcodec hwaccel qsv|
 Blocking:   |  Reproduced by developer:  0
Analyzed by developer:  0|
-+-
Changes (by iEvgeny):

 * Attachment "valgrind.log" added.

-- 
Ticket URL: 
FFmpeg 
FFmpeg issue tracker___
FFmpeg-trac mailing list
FFmpeg-trac@avcodec.org
https://ffmpeg.org/mailman/listinfo/ffmpeg-trac

To unsubscribe, visit link above, or email
ffmpeg-trac-requ...@ffmpeg.org with subject "unsubscribe".

Re: [FFmpeg-trac] #10697(ffmpeg:new): Crash when using incompatible codec and hardware acceleration type

[FFmpeg]

#10697: Crash when using incompatible codec and hardware acceleration type
-+-
 Reporter:  iEvgeny  |Owner:  (none)
 Type:  defect   |   Status:  new
 Priority:  normal   |Component:  ffmpeg
  Version:  git-master   |   Resolution:
 Keywords:  ffmpeg   |   Blocked By:
  avcodec hwaccel qsv|
 Blocking:   |  Reproduced by developer:  0
Analyzed by developer:  0|
-+-
Changes (by iEvgeny):

 * Attachment "gdb.log" added.

-- 
Ticket URL: 
FFmpeg 
FFmpeg issue tracker___
FFmpeg-trac mailing list
FFmpeg-trac@avcodec.org
https://ffmpeg.org/mailman/listinfo/ffmpeg-trac

To unsubscribe, visit link above, or email
ffmpeg-trac-requ...@ffmpeg.org with subject "unsubscribe".

Re: [FFmpeg-trac] #9523(avcodec:open): segment_times splits at I-frames that are not keyframes

[FFmpeg]

#9523: segment_times splits at I-frames that are not keyframes
+---
 Reporter:  TurboLed|Owner:  (none)
 Type:  defect  |   Status:  open
 Priority:  normal  |Component:  avcodec
  Version:  git-master  |   Resolution:
 Keywords:  h264|   Blocked By:
 Blocking:  |  Reproduced by developer:  0
Analyzed by developer:  0   |
+---
Comment (by Tsuyoshi):

 I am also facing the same issue. Is this issue will not be fixed?
 It seems that if stream does not have B-frame, all of I-frame will be
 marked as Keyframe in container.
 Here is the procedure to reproduce this issue.

 1. encode BBB file first 30sec.

ffmpeg -t 30 -i bbb.mp4 -preset ultrafast -profile:v baseline
 -sc_threshold 50 encoded.mp4

 dump all I-frames.
 frame, key_frame, pts, pict_type, coded_picture_number
 {{{
 frame,1,0.00,I,0
 frame,0,0.10,I,3
 frame,0,0.13,I,4
 frame,0,0.17,I,5
 frame,0,0.20,I,6
 frame,0,0.23,I,7
 frame,1,4.07,I,122
 frame,0,4.20,I,126
 frame,0,4.23,I,127
 frame,0,4.47,I,134
 frame,1,12.40,I,372
 frame,1,16.30,I,489
 frame,1,20.17,I,605
 frame,1,27.47,I,824
 }}}
 This is stss Box.
 {{{
 [stss] Size=40 Version=0 Flags=0x00 EntryCount=6 SampleNumber=[1, 123,
 373, 490, 606, 825]
 }}}

 2. remux encoded.mp4 file
 ffmpeg -i encoded.mp4 -c copy remuxed.mp4

 dump all I-frames. This is same as encoded.mp4

 frame, key_frame, pts, pict_type, coded_picture_number
 {{{
 frame,1,0.00,I,0
 frame,0,0.10,I,3
 frame,0,0.13,I,4
 frame,0,0.17,I,5
 frame,0,0.20,I,6
 frame,0,0.23,I,7
 frame,1,4.07,I,122
 frame,0,4.20,I,126
 frame,0,4.23,I,127
 frame,0,4.47,I,134
 frame,1,12.40,I,372
 frame,1,16.30,I,489
 frame,1,20.17,I,605
 frame,1,27.47,I,824
 }}}

 All of I-frames are marked as keyframe in stss box.
 {{{
 [stss] Size=72 Version=0 Flags=0x00 EntryCount=14 SampleNumber=[1, 4,
 5, 6, 7, 8, 123, 127, 128, 135, 373, 490, 606, 825]
 }}}


 I think that h264_parser.c should not include following code. Because It
 is just for the specific camera... If we necessary following code, it
 should be more  restricted code.
 {{{
 // heuristic to detect non marked keyframes
 if (p->ps.sps->ref_frame_count <= 1 && p->ps.pps->ref_count[0] <= 1 &&
 s->pict_type == AV_PICTURE_TYPE_I)
 s->key_frame = 1;
 }}}
-- 
Ticket URL: 
FFmpeg 
FFmpeg issue tracker___
FFmpeg-trac mailing list
FFmpeg-trac@avcodec.org
https://ffmpeg.org/mailman/listinfo/ffmpeg-trac

To unsubscribe, visit link above, or email
ffmpeg-trac-requ...@ffmpeg.org with subject "unsubscribe".

Re: [FFmpeg-trac] #10702(avfilter:new): SEGV bug at /fftools/ffmpeg_enc.c in set_encoder_id in FFmpeg

[FFmpeg]

#10702: SEGV bug at /fftools/ffmpeg_enc.c in set_encoder_id in FFmpeg
--+
 Reporter:  ZengYunxiang  |Owner:  (none)
 Type:  defect|   Status:  new
 Priority:  normal|Component:  avfilter
  Version:  git-master|   Resolution:
 Keywords:  bugs  |   Blocked By:
 Blocking:|  Reproduced by developer:  0
Analyzed by developer:  0 |
--+
Changes (by ZengYunxiang):

 * Attachment "poc6ffmpeg" added.

 POC file
-- 
Ticket URL: 
FFmpeg 
FFmpeg issue tracker___
FFmpeg-trac mailing list
FFmpeg-trac@avcodec.org
https://ffmpeg.org/mailman/listinfo/ffmpeg-trac

To unsubscribe, visit link above, or email
ffmpeg-trac-requ...@ffmpeg.org with subject "unsubscribe".

[FFmpeg-trac] #10702(avfilter:new): SEGV bug at /fftools/ffmpeg_enc.c in set_encoder_id in FFmpeg

[FFmpeg]

#10702: SEGV bug at /fftools/ffmpeg_enc.c in set_encoder_id in FFmpeg
-+-
 Reporter:   | Type:  defect
  ZengYunxiang   |
   Status:  new  | Priority:  normal
Component:  avfilter |  Version:  git-
 |  master
 Keywords:  bugs |   Blocked By:
 Blocking:   |  Reproduced by developer:  0
Analyzed by developer:  0|
-+-
 Summary of the bug:

 Dear developers,
 I found the following SEGV bug on FFmpeg6.1 when using both transpose and
 gradfun filters, please confirm.

 The poc file(poc6ffmpeg) will be attached to this ticket.

 How to reproduce:
 {{{
 git clone https://github.com/FFmpeg/FFmpeg.git ffmpeg6-1
 cd ffmpeg6-1
 git checkout 466799d
 ./configure --cc=clang --cxx=clang++ --ld=clang --enable-debug --toolchain
 =clang-asan
 make -j30

 ./ffmpeg_g -y -i poc6ffmpeg -filter_complex transpose,gradfun tmp.mp4
 }}}
 ASAN Log:
 {{{
 AddressSanitizer:DEADLYSIGNAL
 =
 ==324330==ERROR: AddressSanitizer: SEGV on unknown address 0x6315
 (pc 0x00dfa6df bp 0x7fffc450 sp 0x7fffc238 T0)
 ==324330==The signal is caused by a READ memory access.
 #0 0xdfa6de in ff_gradfun_blur_line_movdqa_sse2
 (/ffmpeg6-1/ffmpeg_g+0xdfa6de)

 AddressSanitizer can not provide additional info.
 SUMMARY: AddressSanitizer: SEGV (/ffmpeg6-1/ffmpeg_g+0xdfa6de) in
 ff_gradfun_blur_line_movdqa_sse2
 ==324330==ABORTING
 }}}

 ffmpeg version:
 {{{
 # ./ffmpeg -version
 ffmpeg version n6.1-3-g466799d4f5 Copyright (c) 2000-2023 the FFmpeg
 developers
 built with clang version 9.0.0 (https://github.com/llvm-mirror/llvm
 c62b24f070c9a4bb1a76409e623042a740cac4cd)
 configuration: --cc=clang --cxx=clang++ --ld=clang --enable-debug
 --toolchain=clang-asan
 libavutil  58. 29.100 / 58. 29.100
 libavcodec 60. 31.102 / 60. 31.102
 libavformat60. 16.100 / 60. 16.100
 libavdevice60.  3.100 / 60.  3.100
 libavfilter 9. 12.100 /  9. 12.100
 libswscale  7.  5.100 /  7.  5.100
 libswresample   4. 12.100 /  4. 12.100
 }}}
 Credit:
 {{{
 Zeng Yunxiang
 }}}
 Thanks for your time!
-- 
Ticket URL: 
FFmpeg 
FFmpeg issue tracker___
FFmpeg-trac mailing list
FFmpeg-trac@avcodec.org
https://ffmpeg.org/mailman/listinfo/ffmpeg-trac

To unsubscribe, visit link above, or email
ffmpeg-trac-requ...@ffmpeg.org with subject "unsubscribe".

Re: [FFmpeg-trac] #10701(avutil:new): memory leaks at ffmpeg6-1/libavutil/mem.c:105:9 in av_malloc in FFmpeg

[FFmpeg]

#10701: memory leaks at ffmpeg6-1/libavutil/mem.c:105:9 in av_malloc in FFmpeg
--+--
 Reporter:  ZengYunxiang  |Owner:  (none)
 Type:  defect|   Status:  new
 Priority:  normal|Component:  avutil
  Version:  git-master|   Resolution:
 Keywords:  bugs  |   Blocked By:
 Blocking:|  Reproduced by developer:  0
Analyzed by developer:  0 |
--+--
Changes (by ZengYunxiang):

 * Attachment "poc8ffmpeg" added.

 POC file
-- 
Ticket URL: 
FFmpeg 
FFmpeg issue tracker___
FFmpeg-trac mailing list
FFmpeg-trac@avcodec.org
https://ffmpeg.org/mailman/listinfo/ffmpeg-trac

To unsubscribe, visit link above, or email
ffmpeg-trac-requ...@ffmpeg.org with subject "unsubscribe".

[FFmpeg-trac] #10701(avutil:new): memory leaks at ffmpeg6-1/libavutil/mem.c:105:9 in av_malloc in FFmpeg

[FFmpeg]

#10701: memory leaks at ffmpeg6-1/libavutil/mem.c:105:9 in av_malloc in FFmpeg
-+-
 Reporter:   | Type:  defect
  ZengYunxiang   |
   Status:  new  | Priority:  normal
Component:  avutil   |  Version:  git-
 |  master
 Keywords:  bugs |   Blocked By:
 Blocking:   |  Reproduced by developer:  0
Analyzed by developer:  0|
-+-
 Summary of the bug:

 Dear developers,
 I found the following memory leaks on FFmpeg6.1 when using colorcorrect
 filter, please confirm.

 The poc file(poc8ffmpeg) will be attached to this ticket.

 How to reproduce:
 {{{
 git clone https://github.com/FFmpeg/FFmpeg.git ffmpeg6-1
 cd ffmpeg6-1
 git checkout 466799d
 ./configure --cc=clang --cxx=clang++ --ld=clang --enable-debug --toolchain
 =clang-asan
 make -j30

 ./ffmpeg_g -y -i poc8ffmpeg -filter_complex colorcorrect tmp.mp4
 }}}
 ASAN Log:
 {{{
 =
 ==1141095==ERROR: LeakSanitizer: detected memory leaks

 Direct leak of 1024 byte(s) in 1 object(s) allocated from:
 #0 0x560cd4de6ab7 in __interceptor_posix_memalign
 (/afltest/ffmpeg6-1/ffmpeg_g+0x925ab7) (BuildId:
 235e8d23658b9f137a6f44e3f2d1bddad7c9bf95)
 #1 0x560cd841f753 in av_malloc
 /afltest/ffmpeg6-1/libavutil/mem.c:105:9
 #2 0x560cd841f753 in av_mallocz
 /afltest/ffmpeg6-1/libavutil/mem.c:256:17
 #3 0x560cd841f753 in av_calloc
 /afltest/ffmpeg6-1/libavutil/mem.c:267:12
 #4 0x560cd4bde02f in config_input
 /afltest/ffmpeg6-1/libavfilter/vf_colorcorrect.c:461:21

 Direct leak of 1024 byte(s) in 1 object(s) allocated from:
 #0 0x560cd4de6ab7 in __interceptor_posix_memalign
 (/afltest/ffmpeg6-1/ffmpeg_g+0x925ab7) (BuildId:
 235e8d23658b9f137a6f44e3f2d1bddad7c9bf95)
 #1 0x560cd841f753 in av_malloc
 /afltest/ffmpeg6-1/libavutil/mem.c:105:9
 #2 0x560cd841f753 in av_mallocz
 /afltest/ffmpeg6-1/libavutil/mem.c:256:17
 #3 0x560cd841f753 in av_calloc
 /afltest/ffmpeg6-1/libavutil/mem.c:267:12
 #4 0x560cd4bddfc9 in config_input
 /afltest/ffmpeg6-1/libavfilter/vf_colorcorrect.c:457:21

 SUMMARY: AddressSanitizer: 2048 byte(s) leaked in 2 allocation(s).
 }}}

 ffmpeg version:
 {{{
 # ./ffmpeg -version
 ffmpeg version n6.1-3-g466799d4f5 Copyright (c) 2000-2023 the FFmpeg
 developers
 built with clang version 9.0.0 (https://github.com/llvm-mirror/llvm
 c62b24f070c9a4bb1a76409e623042a740cac4cd)
 configuration: --cc=clang --cxx=clang++ --ld=clang --enable-debug
 --toolchain=clang-asan
 libavutil  58. 29.100 / 58. 29.100
 libavcodec 60. 31.102 / 60. 31.102
 libavformat60. 16.100 / 60. 16.100
 libavdevice60.  3.100 / 60.  3.100
 libavfilter 9. 12.100 /  9. 12.100
 libswscale  7.  5.100 /  7.  5.100
 libswresample   4. 12.100 /  4. 12.100
 }}}
 Credit:
 {{{
 Zeng Yunxiang
 Song Jiaxuan
 }}}
 Thanks for your time!
-- 
Ticket URL: 
FFmpeg 
FFmpeg issue tracker___
FFmpeg-trac mailing list
FFmpeg-trac@avcodec.org
https://ffmpeg.org/mailman/listinfo/ffmpeg-trac

To unsubscribe, visit link above, or email
ffmpeg-trac-requ...@ffmpeg.org with subject "unsubscribe".

Re: [FFmpeg-trac] #10700(avutil:new): negative-size-param bug at libavutil/samplefmt.c:260:9 in av_samples_set_silence in FFmpeg

[FFmpeg]

#10700: negative-size-param bug at libavutil/samplefmt.c:260:9 in
av_samples_set_silence in FFmpeg
--+--
 Reporter:  ZengYunxiang  |Owner:  (none)
 Type:  defect|   Status:  new
 Priority:  important |Component:  avutil
  Version:  git-master|   Resolution:
 Keywords:  bugs  |   Blocked By:
 Blocking:|  Reproduced by developer:  0
Analyzed by developer:  0 |
--+--
Changes (by ZengYunxiang):

 * Attachment "poc7ffmpeg" added.

 POC file
-- 
Ticket URL: 
FFmpeg 
FFmpeg issue tracker___
FFmpeg-trac mailing list
FFmpeg-trac@avcodec.org
https://ffmpeg.org/mailman/listinfo/ffmpeg-trac

To unsubscribe, visit link above, or email
ffmpeg-trac-requ...@ffmpeg.org with subject "unsubscribe".

[FFmpeg-trac] #10700(avutil:new): negative-size-param bug at libavutil/samplefmt.c:260:9 in av_samples_set_silence in FFmpeg

[FFmpeg]

#10700: negative-size-param bug at libavutil/samplefmt.c:260:9 in
av_samples_set_silence in FFmpeg
-+-
 Reporter:   | Type:  defect
  ZengYunxiang   |
   Status:  new  | Priority:  important
Component:  avutil   |  Version:  git-
 |  master
 Keywords:  bugs |   Blocked By:
 Blocking:   |  Reproduced by developer:  0
Analyzed by developer:  0|
-+-
 Summary of the bug:

 Dear developers,

 I found the following negative-size-param bug on FFmpeg6.1 when using
 afwtdn filter, please confirm.

 The poc file(poc7ffmpeg) will be attached to this ticket.

 How to reproduce:
 {{{
 git clone https://github.com/FFmpeg/FFmpeg.git ffmpeg6-1
 cd ffmpeg6-1
 git checkout 466799d
 ./configure --cc=clang --cxx=clang++ --ld=clang --enable-debug --toolchain
 =clang-asan
 make -j30

 ./ffmpeg_g -y -i poc7ffmpeg -filter_complex afwtdn tmp.mp4
 }}}
 ASAN Log:
 {{{
 ==2197091==ERROR: AddressSanitizer: negative-size-param: (size=-26572)
 #0 0x49813c in __asan_memset /local/mnt/workspace/bcain_clang_bcain-
 ubuntu_23113/llvm/utils/release/final/llvm.src/projects/compiler-
 rt/lib/asan/asan_interceptors_memintrinsics.cc:26:3
 #1 0x3ca380f in av_samples_set_silence
 /ffmpeg6-1/libavutil/samplefmt.c:260:9
 #2 0x557dc9 in ff_default_get_audio_buffer
 /ffmpeg6-1/libavfilter/audio.c:102:5
 #3 0xc80c77 in filter_frame
 /ffmpeg6-1/libavfilter/af_aresample.c:188:21
 #4 0xc80c77 in activate /ffmpeg6-1/libavfilter/af_aresample.c:325:20
 #5 0x5d9e8a in ff_filter_activate
 /ffmpeg6-1/libavfilter/avfilter.c:1330:38
 #6 0x5e9a66 in get_frame_internal
 /ffmpeg6-1/libavfilter/buffersink.c:139:19
 #7 0x5e71f0 in avfilter_graph_request_oldest
 /ffmpeg6-1/libavfilter/avfiltergraph.c:1306:17
 #8 0x4f3801 in fg_transcode_step
 /ffmpeg6-1/fftools/ffmpeg_filter.c:2477:11
 #9 0x535127 in transcode_step /ffmpeg6-1/fftools/ffmpeg.c:1133:20
 #10 0x535127 in transcode /ffmpeg6-1/fftools/ffmpeg.c:1204:15
 #11 0x535127 in main /ffmpeg6-1/fftools/ffmpeg.c:1330:11
 #12 0x77c0d082 in __libc_start_main (/lib/x86_64-linux-
 gnu/libc.so.6+0x24082)
 #13 0x420b4d in _start (/ffmpeg6-1/ffmpeg_g+0x420b4d)

 0x62b1c200 is located 0 bytes inside of 26880-byte region
 [0x62b1c200,0x62b22b00)
 allocated by thread T0 here:
 #0 0x4994e7 in posix_memalign /local/mnt/workspace/bcain_clang_bcain-
 ubuntu_23113/llvm/utils/release/final/llvm.src/projects/compiler-
 rt/lib/asan/asan_malloc_linux.cc:226:3
 #1 0x3c7b0cd in av_malloc /ffmpeg6-1/libavutil/mem.c:105:9
 #2 0x3c30b71 in av_buffer_alloc /ffmpeg6-1/libavutil/buffer.c:82:12
 #3 0x3c32f81 in pool_alloc_buffer /ffmpeg6-1/libavutil/buffer.c:363:26
 #4 0x3c32f81 in av_buffer_pool_get
 /ffmpeg6-1/libavutil/buffer.c:401:15
 #5 0x628496 in ff_frame_pool_get
 /ffmpeg6-1/libavfilter/framepool.c:260:29
 #6 0x557c75 in ff_default_get_audio_buffer
 /ffmpeg6-1/libavfilter/audio.c:85:13
 #7 0xc80c77 in filter_frame
 /ffmpeg6-1/libavfilter/af_aresample.c:188:21
 #8 0xc80c77 in activate /ffmpeg6-1/libavfilter/af_aresample.c:325:20
 #9 0x5d9e8a in ff_filter_activate
 /ffmpeg6-1/libavfilter/avfilter.c:1330:38
 #10 0x5e9a66 in get_frame_internal
 /ffmpeg6-1/libavfilter/buffersink.c:139:19
 #11 0x5e71f0 in avfilter_graph_request_oldest
 /ffmpeg6-1/libavfilter/avfiltergraph.c:1306:17

 SUMMARY: AddressSanitizer: negative-size-param /local/mnt/workspace
 /bcain_clang_bcain-ubuntu_23113/llvm/utils/release/final/llvm.src/projects
 /compiler-rt/lib/asan/asan_interceptors_memintrinsics.cc:26:3 in
 __asan_memset
 ==2197091==ABORTING
 }}}

 ffmpeg version:
 {{{
 # ./ffmpeg -version
 ffmpeg version n6.1-3-g466799d4f5 Copyright (c) 2000-2023 the FFmpeg
 developers
 built with clang version 9.0.0 (https://github.com/llvm-mirror/llvm
 c62b24f070c9a4bb1a76409e623042a740cac4cd)
 configuration: --cc=clang --cxx=clang++ --ld=clang --enable-debug
 --toolchain=clang-asan
 libavutil  58. 29.100 / 58. 29.100
 libavcodec 60. 31.102 / 60. 31.102
 libavformat60. 16.100 / 60. 16.100
 libavdevice60.  3.100 / 60.  3.100
 libavfilter 9. 12.100 /  9. 12.100
 libswscale  7.  5.100 /  7.  5.100
 libswresample   4. 12.100 /  4. 12.100
 }}}
 Credit:
 {{{
 Zeng Yunxiang
 }}}
 Thanks for your time!
-- 
Ticket URL: 
FFmpeg 
FFmpeg issue tracker___
FFmpeg-trac mailing list
FFmpeg-trac@avcodec.org
https://ffmpeg.org/mailman/listinfo/ffmpeg-trac

To unsubscribe, visit link above, or email
ffmpeg-trac-requ...@ffmpeg.org with subject "unsubscribe".

Re: [FFmpeg-trac] #10699(avfilter:new): heap-buffer-overflow at libavfilter/edge_template.c:116:5 in ff_gaussian_blur_8 in FFmpeg

[FFmpeg]

#10699: heap-buffer-overflow at libavfilter/edge_template.c:116:5 in
ff_gaussian_blur_8 in FFmpeg
--+
 Reporter:  ZengYunxiang  |Owner:  (none)
 Type:  defect|   Status:  new
 Priority:  important |Component:  avfilter
  Version:  git-master|   Resolution:
 Keywords:  bugs  |   Blocked By:
 Blocking:|  Reproduced by developer:  0
Analyzed by developer:  0 |
--+
Changes (by ZengYunxiang):

 * Attachment "poc5ffmpeg" added.

 POC file
-- 
Ticket URL: 
FFmpeg 
FFmpeg issue tracker___
FFmpeg-trac mailing list
FFmpeg-trac@avcodec.org
https://ffmpeg.org/mailman/listinfo/ffmpeg-trac

To unsubscribe, visit link above, or email
ffmpeg-trac-requ...@ffmpeg.org with subject "unsubscribe".

[FFmpeg-trac] #10699(avfilter:new): heap-buffer-overflow at libavfilter/edge_template.c:116:5 in ff_gaussian_blur_8 in FFmpeg

[FFmpeg]

#10699: heap-buffer-overflow at libavfilter/edge_template.c:116:5 in
ff_gaussian_blur_8 in FFmpeg
-+-
 Reporter:   | Type:  defect
  ZengYunxiang   |
   Status:  new  | Priority:  important
Component:  avfilter |  Version:  git-
 |  master
 Keywords:  bugs |   Blocked By:
 Blocking:   |  Reproduced by developer:  0
Analyzed by developer:  0|
-+-
 Summary of the bug:

 Dear developers,
 I found the following heap-buffer-overflow bug on FFmpeg6.1 when using
 blurdetect filter, please confirm.

 The poc file(poc5ffmpeg) will be attached to this ticket.

 How to reproduce:
 {{{
 git clone https://github.com/FFmpeg/FFmpeg.git ffmpeg6-1
 cd ffmpeg6-1
 git checkout 466799d
 ./configure --cc=clang --cxx=clang++ --ld=clang --enable-debug --toolchain
 =clang-asan
 make -j30

 ./ffmpeg_g -y -i poc5ffmpeg -filter_complex blurdetect tmp.mp4
 }}}
 ASAN Log:
 {{{
 =
 ==1720809==ERROR: AddressSanitizer: heap-buffer-overflow on address
 0x61e022bb at pc 0x559c66da631a bp 0x7fff763641f0 sp 0x7fff763639c0
 WRITE of size 873 at 0x61e022bb thread T0
 #0 0x559c66da6319 in __asan_memcpy (/ffmpeg6-1/ffmpeg_g+0x924319)
 (BuildId: 235e8d23658b9f137a6f44e3f2d1bddad7c9bf95)
 #1 0x559c67729e03 in ff_gaussian_blur_8
 /ffmpeg6-1/libavfilter/edge_template.c:116:5
 #2 0x559c6700a960 in blurdetect_filter_frame
 /ffmpeg6-1/libavfilter/vf_blurdetect.c:287:9
 #3 0x559c66ef8142 in ff_filter_frame_framed
 /ffmpeg6-1/libavfilter/avfilter.c:969:11
 #4 0x559c66ef8142 in ff_filter_frame_to_filter
 /ffmpeg6-1/libavfilter/avfilter.c:1123:11
 #5 0x559c66ef8142 in ff_filter_activate_default
 /ffmpeg6-1/libavfilter/avfilter.c:1172:20
 #6 0x559c66ef8142 in ff_filter_activate
 /ffmpeg6-1/libavfilter/avfilter.c:1331:11
 #7 0x559c66f0a137 in push_frame
 /ffmpeg6-1/libavfilter/buffersrc.c:167:15
 #8 0x559c66f0a137 in av_buffersrc_add_frame_flags
 /ffmpeg6-1/libavfilter/buffersrc.c:271:15
 #9 0x559c66e0d431 in ifilter_send_frame
 /ffmpeg6-1/fftools/ffmpeg_filter.c:2440:11
 #10 0x559c66de2cbe in send_frame_to_filters
 /ffmpeg6-1/fftools/ffmpeg_dec.c:153:15
 #11 0x559c66de2cbe in dec_packet
 /ffmpeg6-1/fftools/ffmpeg_dec.c:813:19
 #12 0x559c66e53f7b in process_input_packet
 /ffmpeg6-1/fftools/ffmpeg.c:811:15
 #13 0x559c66e51373 in process_input
 /ffmpeg6-1/fftools/ffmpeg.c:1115:11
 #14 0x559c66e51373 in transcode_step
 /ffmpeg6-1/fftools/ffmpeg.c:1142:11
 #15 0x559c66e51373 in transcode /ffmpeg6-1/fftools/ffmpeg.c:1204:15
 #16 0x559c66e51373 in main /ffmpeg6-1/fftools/ffmpeg.c:1330:11
 #17 0x7f29f0e35d8f  (/lib/x86_64-linux-gnu/libc.so.6+0x29d8f)
 (BuildId: a43bfc8428df6623cd498c9c0caeb91aec9be4f9)
 #18 0x7f29f0e35e3f in __libc_start_main (/lib/x86_64-linux-
 gnu/libc.so.6+0x29e3f) (BuildId: a43bfc8428df6623cd498c9c0caeb91aec9be4f9)
 #19 0x559c66d240f4 in _start (/ffmpeg6-1/ffmpeg_g+0x8a20f4) (BuildId:
 235e8d23658b9f137a6f44e3f2d1bddad7c9bf95)

 0x61e022bb is located 0 bytes to the right of 2619-byte region
 [0x61e01880,0x61e022bb)
 allocated by thread T0 here:
 #0 0x559c66da7ab7 in __interceptor_posix_memalign
 (/ffmpeg6-1/ffmpeg_g+0x925ab7) (BuildId:
 235e8d23658b9f137a6f44e3f2d1bddad7c9bf95)
 #1 0x559c6a3dfa5e in av_malloc /ffmpeg6-1/libavutil/mem.c:105:9
 #2 0x559c6700c565 in blurdetect_config_input
 /ffmpeg6-1/libavfilter/vf_blurdetect.c:112:21

 SUMMARY: AddressSanitizer: heap-buffer-overflow
 (/ffmpeg6-1/ffmpeg_g+0x924319) (BuildId:
 235e8d23658b9f137a6f44e3f2d1bddad7c9bf95) in __asan_memcpy
 Shadow bytes around the buggy address:
   0x0c3c7fff8400: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
   0x0c3c7fff8410: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
   0x0c3c7fff8420: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
   0x0c3c7fff8430: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
   0x0c3c7fff8440: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
 =>0x0c3c7fff8450: 00 00 00 00 00 00 00[03]fa fa fa fa fa fa fa fa
   0x0c3c7fff8460: fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa
   0x0c3c7fff8470: fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa
   0x0c3c7fff8480: fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa
   0x0c3c7fff8490: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
   0x0c3c7fff84a0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
 Shadow byte legend (one shadow byte represents 8 application bytes):
   Addressable:   00
   Partially addressable: 01 02 03 04 05 06 07
   Heap left redzone:   fa
   Freed heap region:   fd
   Stack left redzone:  f1
   Stack mid 

[FFmpeg-trac] #10698(ffmpeg:new): VOBsub overlay leaks memory after subtitle stream EOF

[FFmpeg]

#10698: VOBsub overlay leaks memory after subtitle stream EOF
-+-
 Reporter:  Leon | Type:  defect
   Status:  new  | Priority:  normal
Component:  ffmpeg   |  Version:  git-
 Keywords:  overlay  |  master
  framesync memleak memory vobsub|   Blocked By:
 Blocking:   |  Reproduced by developer:  0
Analyzed by developer:  0|
-+-
 Summary of the bug:
 When overlaying VOBsub (`.idx` + `.sub`) onto a video stream using the
 `overlay` video filter, ffmpeg starts to use a lot of memory after the
 subtitle stream has gone EOF.
 This behavior seems to be independent of the video codec, I tested it with
 `h264`, `hevc` and `vp8`, and it happens with all of them.
 It doesn't happen with SubRip `.srt` or MicroDVD `.sub` subtitles (at
 least not with the files I tested), so maybe it only happens with bitmap
 subtitle formats.

 Furthermore, this only happens when at least one of `shortest=1` or
 `eof_action=endall` is used as parameters for the overlay filter.

 How to reproduce:
 Create a test mkv that will be used as an input for the transcode (lower
 values for `-t` suffice, since the subtitles are EOF immediately, but too
 low values may result in the transcode finishing before a significant
 increase in memory usage can be observed):
 {{{
 % ffmpeg -f lavfi -i color -f lavfi -i anullsrc=sample_rate=1 -t 5000 -c:v
 libx264 test.mkv
 }}}
 Download and extract the subtitles I'll link here or below once the ticket
 has been created.
 Run the transcode:
 {{{
 % ffmpeg -i test.mkv -i test.idx -map 0:0 -map 0:1 -map -0:0
 -filter_complex '[0:0][1:0]overlay=shortest=1' out.mkv
 }}}

 Additional information:
 {{{
 % ffmpeg -version
 ffmpeg version N-112854-g44e9cccffa Copyright (c) 2000-2023 the FFmpeg
 developers
 built with gcc 13.2.1 (GCC) 20230801
 configuration: --prefix=/usr --disable-static --disable-stripping
 --disable-htmlpages --enable-amf --enable-avisynth --enable-cuda-llvm
 --enable-lto --enable-fontconfig --enable-gmp --enable-gnutls --enable-gpl
 --enable-ladspa --enable-libaom --enable-libass --enable-libbluray
 --enable-libbs2b --enable-libdav1d --enable-libdrm --enable-libfreetype
 --enable-libfribidi --enable-libgsm --enable-libiec61883 --enable-libjack
 --enable-libjxl --enable-libmodplug --enable-libmp3lame --enable-
 libopencore_amrnb --enable-libopencore_amrwb --enable-libopenjpeg
 --enable-libopenmpt --enable-libopus --enable-libpulse --enable-librav1e
 --enable-librsvg --enable-libsoxr --enable-libspeex --enable-libsrt
 --enable-libssh --enable-libsvtav1 --enable-libtheora --enable-libv4l2
 --enable-libvidstab --enable-libvmaf --enable-libvorbis --enable-libvpl
 --enable-libvpx --enable-libwebp --enable-libx264 --enable-libx265
 --enable-libxcb --enable-libxml2 --enable-libxvid --enable-libzimg
 --enable-nvdec --enable-nvenc --enable-opencl --enable-opengl --enable-
 shared --enable-version3 --enable-vulkan
 libavutil  58. 32.100 / 58. 32.100
 libavcodec 60. 35.100 / 60. 35.100
 libavformat60. 18.100 / 60. 18.100
 libavdevice60.  4.100 / 60.  4.100
 libavfilter 9. 13.100 /  9. 13.100
 libswscale  7.  6.100 /  7.  6.100
 libswresample   4. 13.100 /  4. 13.100
 libpostproc57.  4.100 / 57.  4.100
 }}}

 I also ran the transcode with valgrind massif to try to find out what's
 allocating that much memory. It seems to be frames of the video stream
 (maybe they aren't free'd?)
 Screenshot of massif visualizer:
 [[Image(https://screens.totally.rip/2023/11/6563bebb486bb.png)]]
 I'll also upload the massif outfile via the VideoLAN File Uploader once
 the ticket is created.

 This issue may be related to #6922, as it also uses the `overlay` filter
 with `eof_action=endall`, but I didn't test that.

 Please let me know if I can add any additional useful information!
 Best Regards,
 Leon
-- 
Ticket URL: 
FFmpeg 
FFmpeg issue tracker___
FFmpeg-trac mailing list
FFmpeg-trac@avcodec.org
https://ffmpeg.org/mailman/listinfo/ffmpeg-trac

To unsubscribe, visit link above, or email
ffmpeg-trac-requ...@ffmpeg.org with subject "unsubscribe".

Re: [FFmpeg-trac] #10698(ffmpeg:new): VOBsub overlay leaks memory after subtitle stream EOF

[FFmpeg]

#10698: VOBsub overlay leaks memory after subtitle stream EOF
-+-
 Reporter:  Leon |Owner:  (none)
 Type:  defect   |   Status:  new
 Priority:  normal   |Component:  ffmpeg
  Version:  git-master   |   Resolution:
 Keywords:  overlay  |   Blocked By:
  framesync memleak memory vobsub|
 Blocking:   |  Reproduced by developer:  0
Analyzed by developer:  0|
-+-
Description changed by Leon:

Old description:

> Summary of the bug:
> When overlaying VOBsub (`.idx` + `.sub`) onto a video stream using the
> `overlay` video filter, ffmpeg starts to use a lot of memory after the
> subtitle stream has gone EOF.
> This behavior seems to be independent of the video codec, I tested it
> with `h264`, `hevc` and `vp8`, and it happens with all of them.
> It doesn't happen with SubRip `.srt` or MicroDVD `.sub` subtitles (at
> least not with the files I tested), so maybe it only happens with bitmap
> subtitle formats.
>
> Furthermore, this only happens when at least one of `shortest=1` or
> `eof_action=endall` is used as parameters for the overlay filter.
>
> How to reproduce:
> Create a test mkv that will be used as an input for the transcode (lower
> values for `-t` suffice, since the subtitles are EOF immediately, but too
> low values may result in the transcode finishing before a significant
> increase in memory usage can be observed):
> {{{
> % ffmpeg -f lavfi -i color -f lavfi -i anullsrc=sample_rate=1 -t 5000
> -c:v libx264 test.mkv
> }}}
> Download and extract the subtitles I'll link here or below once the
> ticket has been created.
> Run the transcode:
> {{{
> % ffmpeg -i test.mkv -i test.idx -map 0:0 -map 0:1 -map -0:0
> -filter_complex '[0:0][1:0]overlay=shortest=1' out.mkv
> }}}
>
> Additional information:
> {{{
> % ffmpeg -version
> ffmpeg version N-112854-g44e9cccffa Copyright (c) 2000-2023 the FFmpeg
> developers
> built with gcc 13.2.1 (GCC) 20230801
> configuration: --prefix=/usr --disable-static --disable-stripping
> --disable-htmlpages --enable-amf --enable-avisynth --enable-cuda-llvm
> --enable-lto --enable-fontconfig --enable-gmp --enable-gnutls --enable-
> gpl --enable-ladspa --enable-libaom --enable-libass --enable-libbluray
> --enable-libbs2b --enable-libdav1d --enable-libdrm --enable-libfreetype
> --enable-libfribidi --enable-libgsm --enable-libiec61883 --enable-libjack
> --enable-libjxl --enable-libmodplug --enable-libmp3lame --enable-
> libopencore_amrnb --enable-libopencore_amrwb --enable-libopenjpeg
> --enable-libopenmpt --enable-libopus --enable-libpulse --enable-librav1e
> --enable-librsvg --enable-libsoxr --enable-libspeex --enable-libsrt
> --enable-libssh --enable-libsvtav1 --enable-libtheora --enable-libv4l2
> --enable-libvidstab --enable-libvmaf --enable-libvorbis --enable-libvpl
> --enable-libvpx --enable-libwebp --enable-libx264 --enable-libx265
> --enable-libxcb --enable-libxml2 --enable-libxvid --enable-libzimg
> --enable-nvdec --enable-nvenc --enable-opencl --enable-opengl --enable-
> shared --enable-version3 --enable-vulkan
> libavutil  58. 32.100 / 58. 32.100
> libavcodec 60. 35.100 / 60. 35.100
> libavformat60. 18.100 / 60. 18.100
> libavdevice60.  4.100 / 60.  4.100
> libavfilter 9. 13.100 /  9. 13.100
> libswscale  7.  6.100 /  7.  6.100
> libswresample   4. 13.100 /  4. 13.100
> libpostproc57.  4.100 / 57.  4.100
> }}}
>
> I also ran the transcode with valgrind massif to try to find out what's
> allocating that much memory. It seems to be frames of the video stream
> (maybe they aren't free'd?)
> Screenshot of massif visualizer:
> [[Image(https://screens.totally.rip/2023/11/6563bebb486bb.png)]]
> I'll also upload the massif outfile via the VideoLAN File Uploader once
> the ticket is created.
>
> This issue may be related to #6922, as it also uses the `overlay` filter
> with `eof_action=endall`, but I didn't test that.
>
> Please let me know if I can add any additional useful information!
> Best Regards,
> Leon

New description:

 Summary of the bug:
 When overlaying VOBsub (`.idx` + `.sub`) onto a video stream using the
 `overlay` video filter, ffmpeg starts to use a lot of memory after the
 subtitle stream has gone EOF.
 This behavior seems to be independent of the video codec, I tested it with
 `h264`, `hevc` and `vp8`, and it happens with all of them.
 It doesn't happen with SubRip `.srt` or MicroDVD `.sub` subtitles (at
 least not with the files I tested), so maybe it only happens with bitmap
 subtitle formats.

 Furthermore, this only happens when at least one of `shortest=1` or
 `eof_action=endall` is used as parameters for the overlay filter.

 How to reproduce:
 Create a test mkv that will be used as an 

Re: [FFmpeg-trac] #10698(ffmpeg:new): VOBsub overlay leaks memory after subtitle stream EOF

[FFmpeg]

#10698: VOBsub overlay leaks memory after subtitle stream EOF
-+-
 Reporter:  Leon |Owner:  (none)
 Type:  defect   |   Status:  new
 Priority:  normal   |Component:  ffmpeg
  Version:  git-master   |   Resolution:
 Keywords:  overlay  |   Blocked By:
  framesync memleak memory vobsub|
 Blocking:   |  Reproduced by developer:  0
Analyzed by developer:  0|
-+-
Changes (by Leon):

 * Attachment "massif.out.59344" added.

 valgrind massif of a memory leak that happens with the overlay filter.
-- 
Ticket URL: 
FFmpeg 
FFmpeg issue tracker___
FFmpeg-trac mailing list
FFmpeg-trac@avcodec.org
https://ffmpeg.org/mailman/listinfo/ffmpeg-trac

To unsubscribe, visit link above, or email
ffmpeg-trac-requ...@ffmpeg.org with subject "unsubscribe".

Re: [FFmpeg-trac] #10698(ffmpeg:new): VOBsub overlay leaks memory after subtitle stream EOF

[FFmpeg]

#10698: VOBsub overlay leaks memory after subtitle stream EOF
-+-
 Reporter:  Leon |Owner:  (none)
 Type:  defect   |   Status:  new
 Priority:  normal   |Component:  ffmpeg
  Version:  git-master   |   Resolution:
 Keywords:  overlay  |   Blocked By:
  framesync memleak memory vobsub|
 Blocking:   |  Reproduced by developer:  0
Analyzed by developer:  0|
-+-
Changes (by Leon):

 * Attachment "overlay-memleak-subs.zip" added.

 VOBsubs for easy reproduction of a memory leak that happens with the
 overlay filter.
-- 
Ticket URL: 
FFmpeg 
FFmpeg issue tracker___
FFmpeg-trac mailing list
FFmpeg-trac@avcodec.org
https://ffmpeg.org/mailman/listinfo/ffmpeg-trac

To unsubscribe, visit link above, or email
ffmpeg-trac-requ...@ffmpeg.org with subject "unsubscribe".

Re: [FFmpeg-trac] #10694(avfilter:closed): hb_font_destroy exception on multi thread

[FFmpeg]

#10694: hb_font_destroy exception on multi thread
--+
 Reporter:  harf  |Owner:  (none)
 Type:  defect|   Status:  closed
 Priority:  minor |Component:  avfilter
  Version:  6.0   |   Resolution:  invalid
 Keywords:  harfbuzz  |   Blocked By:
 Blocking:|  Reproduced by developer:  0
Analyzed by developer:  0 |
--+
Comment (by harf):

 To fix the issue you need:
 pthread_mutex_lock();
 av_buffersink_get_frame_flags(...);
 pthread_mutex_unlock();

 ffmpeg version 6.0 uses harfbuzz lib, which uses freetype lib which has an
 issue on multithead access.
-- 
Ticket URL: 
FFmpeg 
FFmpeg issue tracker___
FFmpeg-trac mailing list
FFmpeg-trac@avcodec.org
https://ffmpeg.org/mailman/listinfo/ffmpeg-trac

To unsubscribe, visit link above, or email
ffmpeg-trac-requ...@ffmpeg.org with subject "unsubscribe".

Re: [FFmpeg-trac] #10694(avfilter:closed): hb_font_destroy exception on multi thread

[FFmpeg]

#10694: hb_font_destroy exception on multi thread
--+
 Reporter:  harf  |Owner:  (none)
 Type:  defect|   Status:  closed
 Priority:  minor |Component:  avfilter
  Version:  6.0   |   Resolution:  fixed
 Keywords:  harfbuzz  |   Blocked By:
 Blocking:|  Reproduced by developer:  0
Analyzed by developer:  0 |
--+
Changes (by harf):

 * resolution:  invalid => fixed

-- 
Ticket URL: 
FFmpeg 
FFmpeg issue tracker___
FFmpeg-trac mailing list
FFmpeg-trac@avcodec.org
https://ffmpeg.org/mailman/listinfo/ffmpeg-trac

To unsubscribe, visit link above, or email
ffmpeg-trac-requ...@ffmpeg.org with subject "unsubscribe".

Re: [FFmpeg-trac] #10697(ffmpeg:new): Crash when using incompatible codec and hardware acceleration type

[FFmpeg]

#10697: Crash when using incompatible codec and hardware acceleration type
-+-
 Reporter:  iEvgeny  |Owner:  (none)
 Type:  defect   |   Status:  new
 Priority:  normal   |Component:  ffmpeg
  Version:  git-master   |   Resolution:
 Keywords:  ffmpeg   |   Blocked By:
  avcodec hwaccel qsv|
 Blocking:   |  Reproduced by developer:  0
Analyzed by developer:  0|
-+-
Changes (by iEvgeny):

 * Attachment "gdb.log" added.

-- 
Ticket URL: 
FFmpeg 
FFmpeg issue tracker___
FFmpeg-trac mailing list
FFmpeg-trac@avcodec.org
https://ffmpeg.org/mailman/listinfo/ffmpeg-trac

To unsubscribe, visit link above, or email
ffmpeg-trac-requ...@ffmpeg.org with subject "unsubscribe".

Re: [FFmpeg-trac] #10697(ffmpeg:new): Crash when using incompatible codec and hardware acceleration type

[FFmpeg]

#10697: Crash when using incompatible codec and hardware acceleration type
-+-
 Reporter:  iEvgeny  |Owner:  (none)
 Type:  defect   |   Status:  new
 Priority:  normal   |Component:  ffmpeg
  Version:  git-master   |   Resolution:
 Keywords:  ffmpeg   |   Blocked By:
  avcodec hwaccel qsv|
 Blocking:   |  Reproduced by developer:  0
Analyzed by developer:  0|
-+-
Changes (by iEvgeny):

 * Attachment "ffmpeg-20231126-220246.log" added.

-- 
Ticket URL: <https://trac.ffmpeg.org/ticket/10697>
FFmpeg <https://ffmpeg.org>
FFmpeg issue tracker___
FFmpeg-trac mailing list
FFmpeg-trac@avcodec.org
https://ffmpeg.org/mailman/listinfo/ffmpeg-trac

To unsubscribe, visit link above, or email
ffmpeg-trac-requ...@ffmpeg.org with subject "unsubscribe".

[FFmpeg-trac] #10697(ffmpeg:new): Crash when using incompatible codec and hardware acceleration type

[FFmpeg]

#10697: Crash when using incompatible codec and hardware acceleration type
-+-
 Reporter:  iEvgeny  | Type:  defect
   Status:  new  | Priority:  normal
Component:  ffmpeg   |  Version:  git-
 Keywords:  ffmpeg   |  master
  avcodec hwaccel qsv|   Blocked By:
 Blocking:   |  Reproduced by developer:  0
Analyzed by developer:  0|
-+-
 Attempting to use an incompatible VAAPI hardware device and QSV codec
 causes FFmpeg to crash.

 How to reproduce:
 {{{
 % ffmpeg -hwaccel vaapi -c:v h264_qsv -i rtmp://live.a71.ru/demo/0 -f null
 -
 }}}

 Output:
 {{{
 ffmpeg version N-112838-g7212466e73 Copyright (c) 2000-2023 the FFmpeg
 developers
   built with gcc 11 (Ubuntu 11.4.0-1ubuntu1~22.04)
   configuration: --prefix=/home/evgeny/ffmpeg_build --pkg-config-
 flags=--static --extra-cflags=-I/home/evgeny/ffmpeg_build/include --extra-
 ldflags=-L/home/evgeny/ffmpeg_build/lib --extra-libs='-lpthread -lm'
 --ld=g++ --bindir=/home/evgeny/bin --enable-gpl --enable-gnutls --enable-
 libx264 --enable-nonfree --enable-libvpl
   libavutil  58. 32.100 / 58. 32.100
   libavcodec 60. 34.100 / 60. 34.100
   libavformat60. 17.100 / 60. 17.100
   libavdevice60.  4.100 / 60.  4.100
   libavfilter 9. 13.100 /  9. 13.100
   libswscale  7.  6.100 /  7.  6.100
   libswresample   4. 13.100 /  4. 13.100
   libpostproc57.  4.100 / 57.  4.100
 Input #0, flv, from 'rtmp://live.a71.ru/demo/0':
   Metadata:
 |RtmpSampleAccess: true
 Server  : NGINX RTMP (github.com/arut/nginx-rtmp-module)
 displayWidth: 1920
 displayHeight   : 1080
 fps : 10
 profile :
 level   :
   Duration: 00:00:00.00, start: 282846.534000, bitrate: N/A
   Stream #0:0: Video: h264 (Main), yuvj420p(pc, bt709, progressive),
 1920x1080 [SAR 1:1 DAR 16:9], 10 fps, 20 tbr, 1k tbn
 Stream mapping:
   Stream #0:0 -> #0:0 (h264 (h264_qsv) -> wrapped_avframe (native))
 Press [q] to stop, [?] for help
 Segmentation fault (core dumped)
 }}}
-- 
Ticket URL: 
FFmpeg 
FFmpeg issue tracker___
FFmpeg-trac mailing list
FFmpeg-trac@avcodec.org
https://ffmpeg.org/mailman/listinfo/ffmpeg-trac

To unsubscribe, visit link above, or email
ffmpeg-trac-requ...@ffmpeg.org with subject "unsubscribe".

Re: [FFmpeg-trac] #10696(undetermined:new): 44.1 16-bit monkey's audio .ape file decodes with blasts of noise

[FFmpeg]

#10696: 44.1 16-bit monkey's audio .ape file decodes with blasts of noise
-+-
 Reporter:   |Owner:  (none)
  therentabrain  |
 Type:  defect   |   Status:  new
 Priority:  normal   |Component:
 |  undetermined
  Version:  unspecified  |   Resolution:
 Keywords:  monkey's |   Blocked By:
  audio .ape |
 Blocking:   |  Reproduced by developer:  0
Analyzed by developer:  0|
-+-
Description changed by therentabrain:

Old description:

> Summary of the bug:
> Occasional .ape files created by Monkey's Audio 3.88 in Extra High mode
> are mangled when read by ffmpeg, as containing sections of white noise
> and/or silence.  Out of about 60 files in my tests, it happened 3 times.
>
> Files created by Monkey's Audio 3.99 did not seem to have this problem in
> my experience.  Still, the problem files test with no errors and can be
> successfully played in Winamp or decompressed by either version of MA
> without a problem.  Only ffmpeg fails and only under this specific
> situation.
>

> How to reproduce:
> {{{
> I:\>ffmpeg -i themagicwannago.ape themagicwannago.wav
> ffmpeg version 2023-11-22-git-0008e1c5d5-full_build-www.gyan.dev
> Copyright (c) 2000-2023 the FFmpeg developers
>   built with gcc 12.2.0 (Rev10, Built by MSYS2 project)
>   configuration: --enable-gpl --enable-version3 --enable-static --pkg-
> config=pkgconf --disable-w32threads --disable-autodetect --enable-
> fontconfig --enable-iconv --enable-gnutls --enable-libxml2 --enable-gmp
> --enable-bzlib --enable-lzma --enable-libsnappy --enable-zlib --enable-
> librist --enable-libsrt --enable-libssh --enable-libzmq --enable-avisynth
> --enable-libbluray --enable-libcaca --enable-sdl2 --enable-libaribb24
> --enable-libaribcaption --enable-libdav1d --enable-libdavs2 --enable-
> libuavs3d --enable-libzvbi --enable-librav1e --enable-libsvtav1 --enable-
> libwebp --enable-libx264 --enable-libx265 --enable-libxavs2 --enable-
> libxvid --enable-libaom --enable-libjxl --enable-libopenjpeg --enable-
> libvpx --enable-mediafoundation --enable-libass --enable-frei0r --enable-
> libfreetype --enable-libfribidi --enable-libharfbuzz --enable-liblensfun
> --enable-libvidstab --enable-libvmaf --enable-libzimg --enable-amf
> --enable-cuda-llvm --enable-cuvid --enable-ffnvcodec --enable-nvdec
> --enable-nvenc --enable-dxva2 --enable-d3d11va --enable-libvpl --enable-
> libshaderc --enable-vulkan --enable-libplacebo --enable-opencl --enable-
> libcdio --enable-libgme --enable-libmodplug --enable-libopenmpt --enable-
> libopencore-amrwb --enable-libmp3lame --enable-libshine --enable-
> libtheora --enable-libtwolame --enable-libvo-amrwbenc --enable-libcodec2
> --enable-libilbc --enable-libgsm --enable-libopencore-amrnb --enable-
> libopus --enable-libspeex --enable-libvorbis --enable-ladspa --enable-
> libbs2b --enable-libflite --enable-libmysofa --enable-librubberband
> --enable-libsoxr --enable-chromaprint
>   libavutil  58. 32.100 / 58. 32.100
>   libavcodec 60. 34.100 / 60. 34.100
>   libavformat60. 17.100 / 60. 17.100
>   libavdevice60.  4.100 / 60.  4.100
>   libavfilter 9. 13.100 /  9. 13.100
>   libswscale  7.  6.100 /  7.  6.100
>   libswresample   4. 13.100 /  4. 13.100
>   libpostproc57.  4.100 / 57.  4.100
> Input #0, ape, from 'themagicwannago.ape':
>   Duration: 00:00:01.87, start: 0.00, bitrate: 370 kb/s
>   Stream #0:0: Audio: ape (APE  / 0x20455041), 44100 Hz, stereo, s16p
> Stream mapping:
>   Stream #0:0 -> #0:0 (ape (native) -> pcm_s16le (native))
> Press [q] to stop, [?] for help
> Output #0, wav, to 'themagicwannago.wav':
>   Metadata:
> ISFT: Lavf60.17.100
>   Stream #0:0: Audio: pcm_s16le ([1][0][0][0] / 0x0001), 44100 Hz,
> stereo, s16, 1411 kb/s
> Metadata:
>   encoder : Lavc60.34.100 pcm_s16le
> [out#0/wav @ 017fc96c8880] video:0kB audio:322kB subtitle:0kB other
> streams:0kB global headers:0kB muxing overhead: 0.023639%
> size= 322kB time=00:00:01.67 bitrate=1579.3kbits/s speed= 101x
> }}}
>
> File info from Monkey's Audio 3.88:
>
> {{{
> Format Info
> Version: 3.8
> Mode: Extra High
> Format Flags: 6
> Tag: None
> Audio Info
> Sample Rate: 44100
> Channels: 2
> Bits Per Sample: 16
> Peak Level: 22186
> Length / Size Info
> Length: 0:01
> File Size: 0.00 MB
> Compression: 26.22%
> }}}
>
> Monkey's Audio 3.99 reports no errors with it either, and both versions
> of MA have no problems decoding it correctly.  Then, the resulting WAV
> can then be turned into FLAC etc by ffmpeg just fine.
>
> ''I did notice that using MediaInfo v0.7.80, the number of tracks is
> 

[FFmpeg-trac] #10696(undetermined:new): 44.1 16-bit monkey's audio .ape file decodes with blasts of noise

[FFmpeg]

#10696: 44.1 16-bit monkey's audio .ape file decodes with blasts of noise
-+-
 Reporter:   | Type:  defect
  therentabrain  |
   Status:  new  | Priority:  normal
Component:   |  Version:
  undetermined   |  unspecified
 Keywords:  monkey's |   Blocked By:
  audio .ape |
 Blocking:   |  Reproduced by developer:  0
Analyzed by developer:  0|
-+-
 Summary of the bug:
 Occasional .ape files created by Monkey's Audio 3.88 in Extra High mode
 are mangled when read by ffmpeg, as containing sections of white noise
 and/or silence.  Out of about 60 files in my tests, it happened 3 times.

 Files created by Monkey's Audio 3.99 did not seem to have this problem in
 my experience.  Still, the problem files test with no errors and can be
 successfully played in Winamp or decompressed by either version of MA
 without a problem.  Only ffmpeg fails and only under this specific
 situation.


 How to reproduce:
 {{{
 I:\>ffmpeg -i themagicwannago.ape themagicwannago.wav
 ffmpeg version 2023-11-22-git-0008e1c5d5-full_build-www.gyan.dev Copyright
 (c) 2000-2023 the FFmpeg developers
   built with gcc 12.2.0 (Rev10, Built by MSYS2 project)
   configuration: --enable-gpl --enable-version3 --enable-static --pkg-
 config=pkgconf --disable-w32threads --disable-autodetect --enable-
 fontconfig --enable-iconv --enable-gnutls --enable-libxml2 --enable-gmp
 --enable-bzlib --enable-lzma --enable-libsnappy --enable-zlib --enable-
 librist --enable-libsrt --enable-libssh --enable-libzmq --enable-avisynth
 --enable-libbluray --enable-libcaca --enable-sdl2 --enable-libaribb24
 --enable-libaribcaption --enable-libdav1d --enable-libdavs2 --enable-
 libuavs3d --enable-libzvbi --enable-librav1e --enable-libsvtav1 --enable-
 libwebp --enable-libx264 --enable-libx265 --enable-libxavs2 --enable-
 libxvid --enable-libaom --enable-libjxl --enable-libopenjpeg --enable-
 libvpx --enable-mediafoundation --enable-libass --enable-frei0r --enable-
 libfreetype --enable-libfribidi --enable-libharfbuzz --enable-liblensfun
 --enable-libvidstab --enable-libvmaf --enable-libzimg --enable-amf
 --enable-cuda-llvm --enable-cuvid --enable-ffnvcodec --enable-nvdec
 --enable-nvenc --enable-dxva2 --enable-d3d11va --enable-libvpl --enable-
 libshaderc --enable-vulkan --enable-libplacebo --enable-opencl --enable-
 libcdio --enable-libgme --enable-libmodplug --enable-libopenmpt --enable-
 libopencore-amrwb --enable-libmp3lame --enable-libshine --enable-libtheora
 --enable-libtwolame --enable-libvo-amrwbenc --enable-libcodec2 --enable-
 libilbc --enable-libgsm --enable-libopencore-amrnb --enable-libopus
 --enable-libspeex --enable-libvorbis --enable-ladspa --enable-libbs2b
 --enable-libflite --enable-libmysofa --enable-librubberband --enable-
 libsoxr --enable-chromaprint
   libavutil  58. 32.100 / 58. 32.100
   libavcodec 60. 34.100 / 60. 34.100
   libavformat60. 17.100 / 60. 17.100
   libavdevice60.  4.100 / 60.  4.100
   libavfilter 9. 13.100 /  9. 13.100
   libswscale  7.  6.100 /  7.  6.100
   libswresample   4. 13.100 /  4. 13.100
   libpostproc57.  4.100 / 57.  4.100
 Input #0, ape, from 'themagicwannago.ape':
   Duration: 00:00:01.87, start: 0.00, bitrate: 370 kb/s
   Stream #0:0: Audio: ape (APE  / 0x20455041), 44100 Hz, stereo, s16p
 Stream mapping:
   Stream #0:0 -> #0:0 (ape (native) -> pcm_s16le (native))
 Press [q] to stop, [?] for help
 Output #0, wav, to 'themagicwannago.wav':
   Metadata:
 ISFT: Lavf60.17.100
   Stream #0:0: Audio: pcm_s16le ([1][0][0][0] / 0x0001), 44100 Hz, stereo,
 s16, 1411 kb/s
 Metadata:
   encoder : Lavc60.34.100 pcm_s16le
 [out#0/wav @ 017fc96c8880] video:0kB audio:322kB subtitle:0kB other
 streams:0kB global headers:0kB muxing overhead: 0.023639%
 size= 322kB time=00:00:01.67 bitrate=1579.3kbits/s speed= 101x
 }}}

 File info from Monkey's Audio 3.88:

 {{{
 Format Info
 Version: 3.8
 Mode: Extra High
 Format Flags: 6
 Tag: None
 Audio Info
 Sample Rate: 44100
 Channels: 2
 Bits Per Sample: 16
 Peak Level: 22186
 Length / Size Info
 Length: 0:01
 File Size: 0.00 MB
 Compression: 26.22%
 }}}

 Monkey's Audio 3.99 reports no errors with it either, and both versions of
 MA have no problems decoding it correctly.  Then, the resulting WAV can
 then be turned into FLAC etc by ffmpeg just fine.

 ''I did notice that using MediaInfo v0.7.80, the number of tracks is
 hugely incorrect on these files.  The attached test file here shows as
 2,500 tracks in MediaInfo, when it should say two.  In my limited
 experience, MediaInfo is capable of seeing the correct number of tracks in
 

Re: [FFmpeg-trac] #10696(undetermined:new): 44.1 16-bit monkey's audio .ape file decodes with blasts of noise

[FFmpeg]

#10696: 44.1 16-bit monkey's audio .ape file decodes with blasts of noise
-+-
 Reporter:   |Owner:  (none)
  therentabrain  |
 Type:  defect   |   Status:  new
 Priority:  normal   |Component:
 |  undetermined
  Version:  unspecified  |   Resolution:
 Keywords:  monkey's |   Blocked By:
  audio .ape |
 Blocking:   |  Reproduced by developer:  0
Analyzed by developer:  0|
-+-
Changes (by therentabrain):

 * Attachment "themagicwannago.wav" added.

 Output of ffmpeg, just noise
-- 
Ticket URL: 
FFmpeg 
FFmpeg issue tracker___
FFmpeg-trac mailing list
FFmpeg-trac@avcodec.org
https://ffmpeg.org/mailman/listinfo/ffmpeg-trac

To unsubscribe, visit link above, or email
ffmpeg-trac-requ...@ffmpeg.org with subject "unsubscribe".

Re: [FFmpeg-trac] #10696(undetermined:new): 44.1 16-bit monkey's audio .ape file decodes with blasts of noise

[FFmpeg]

#10696: 44.1 16-bit monkey's audio .ape file decodes with blasts of noise
-+-
 Reporter:   |Owner:  (none)
  therentabrain  |
 Type:  defect   |   Status:  new
 Priority:  normal   |Component:
 |  undetermined
  Version:  unspecified  |   Resolution:
 Keywords:  monkey's |   Blocked By:
  audio .ape |
 Blocking:   |  Reproduced by developer:  0
Analyzed by developer:  0|
-+-
Changes (by therentabrain):

 * Attachment "themagicwannago.ape" added.

 ape file made with v2.88, tests as valid and plays fine, chokes in ffmpeg
-- 
Ticket URL: 
FFmpeg 
FFmpeg issue tracker___
FFmpeg-trac mailing list
FFmpeg-trac@avcodec.org
https://ffmpeg.org/mailman/listinfo/ffmpeg-trac

To unsubscribe, visit link above, or email
ffmpeg-trac-requ...@ffmpeg.org with subject "unsubscribe".

Re: [FFmpeg-trac] #10694(avfilter:closed): hb_font_destroy exception on multi thread

[FFmpeg]

#10694: hb_font_destroy exception on multi thread
--+
 Reporter:  harf  |Owner:  (none)
 Type:  defect|   Status:  closed
 Priority:  minor |Component:  avfilter
  Version:  6.0   |   Resolution:  invalid
 Keywords:  harfbuzz  |   Blocked By:
 Blocking:|  Reproduced by developer:  0
Analyzed by developer:  0 |
--+
Changes (by Elon Musk):

 * priority:  critical => minor
 * status:  new => closed
 * resolution:   => invalid

Comment:

 No valid ticket, Missing all information.
-- 
Ticket URL: 
FFmpeg 
FFmpeg issue tracker___
FFmpeg-trac mailing list
FFmpeg-trac@avcodec.org
https://ffmpeg.org/mailman/listinfo/ffmpeg-trac

To unsubscribe, visit link above, or email
ffmpeg-trac-requ...@ffmpeg.org with subject "unsubscribe".

Re: [FFmpeg-trac] #10686(avfilter:closed): heap-buffer-overflow at libavfilter/asrc_afirsrc.c:495:30 in config_eq_output in FFmpeg

[FFmpeg]

#10686: heap-buffer-overflow at libavfilter/asrc_afirsrc.c:495:30 in
config_eq_output in FFmpeg
--+
 Reporter:  ZengYunxiang  |Owner:  (none)
 Type:  defect|   Status:  closed
 Priority:  critical  |Component:  avfilter
  Version:  git-master|   Resolution:  fixed
 Keywords:  bugs  |   Blocked By:
 Blocking:|  Reproduced by developer:  0
Analyzed by developer:  0 |
--+
Changes (by Elon Musk):

 * status:  new => closed
 * resolution:   => fixed

-- 
Ticket URL: 
FFmpeg 
FFmpeg issue tracker___
FFmpeg-trac mailing list
FFmpeg-trac@avcodec.org
https://ffmpeg.org/mailman/listinfo/ffmpeg-trac

To unsubscribe, visit link above, or email
ffmpeg-trac-requ...@ffmpeg.org with subject "unsubscribe".

Re: [FFmpeg-trac] #10691(undetermined:closed): heap-buffer-overflow at libavfilter/af_dialoguenhance.c:261:5 in de_stereo in FFmpeg

[FFmpeg]

#10691: heap-buffer-overflow at libavfilter/af_dialoguenhance.c:261:5 in 
de_stereo
in FFmpeg
-+-
 Reporter:   |Owner:  (none)
  ZengYunxiang   |
 Type:  defect   |   Status:  closed
 Priority:  important|Component:
 |  undetermined
  Version:  git-master   |   Resolution:  fixed
 Keywords:  bugs |   Blocked By:
 Blocking:   |  Reproduced by developer:  0
Analyzed by developer:  0|
-+-
Changes (by Elon Musk):

 * status:  new => closed
 * resolution:   => fixed

-- 
Ticket URL: 
FFmpeg 
FFmpeg issue tracker___
FFmpeg-trac mailing list
FFmpeg-trac@avcodec.org
https://ffmpeg.org/mailman/listinfo/ffmpeg-trac

To unsubscribe, visit link above, or email
ffmpeg-trac-requ...@ffmpeg.org with subject "unsubscribe".

Re: [FFmpeg-trac] #10693(documentation:new): Filters/libvmaf: `pool` parameter missing

[FFmpeg]

#10693: Filters/libvmaf: `pool` parameter missing
-+-
 Reporter:  t-nil|Owner:  (none)
 Type:  defect   |   Status:  new
 Priority:  normal   |Component:
 |  documentation
  Version:  git-master   |   Resolution:
 Keywords:  libvmaf  |   Blocked By:
  filters doc docs   |
 Blocking:   |  Reproduced by developer:  0
Analyzed by developer:  0|
-+-
Comment (by Gyan):

 Looks like it was deleted by mistake. The same commit that removed the doc
 entry added a helper function for the option :)

 Will restore it.
-- 
Ticket URL: 
FFmpeg 
FFmpeg issue tracker___
FFmpeg-trac mailing list
FFmpeg-trac@avcodec.org
https://ffmpeg.org/mailman/listinfo/ffmpeg-trac

To unsubscribe, visit link above, or email
ffmpeg-trac-requ...@ffmpeg.org with subject "unsubscribe".