[FFmpeg-trac] #6530(ffmpeg:new): Excessive Memory Usage

FFmpeg trac at avcodec.org
Mon Jul 17 10:05:42 EEST 2017


#6530: Excessive Memory Usage
---------------------------------+---------------------------------------
             Reporter:  WayToGo  |                     Type:  defect
               Status:  new      |                 Priority:  critical
            Component:  ffmpeg   |                  Version:  unspecified
             Keywords:  Memory   |               Blocked By:
             Blocking:           |  Reproduced by developer:  0
Analyzed by developer:  0        |
---------------------------------+---------------------------------------
 Summary of the bug:
 How to reproduce:
 {{{
 % ffmpeg -i input.mp4 -crf 25 -vf scale=-2:234 -preset faster -c:a copy
 -c:s copy -movflags +faststart -threads 1 234.mp4;

 ffmpeg version N-86761-g80b9e40b6f-static http://johnvansickle.com/ffmpeg/
 Copyright (c) 2000-2017 the FFmpeg developers
   built with gcc 5.4.1 (Debian 5.4.1-11) 20170519
   configuration: --enable-gpl --enable-version3 --enable-static --disable-
 debug --disable-ffplay --disable-indev=sndio --disable-outdev=sndio
 --cc=gcc-5 --enable-fontconfig --enable-frei0r --enable-gnutls --enable-
 gray --enable-libass --enable-libfreetype --enable-libfribidi --enable-
 libmp3lame --enable-libopencore-amrnb --enable-libopencore-amrwb --enable-
 libopenjpeg --enable-libopus --enable-librtmp --enable-libsoxr --enable-
 libspeex --enable-libtheora --enable-libvidstab --enable-libvo-amrwbenc
 --enable-libvorbis --enable-libvpx --enable-libwebp --enable-libx264
 --enable-libx265 --enable-libxvid --enable-libzimg
   libavutil      55. 67.100 / 55. 67.100
   libavcodec     57.100.104 / 57.100.104
   libavformat    57. 75.100 / 57. 75.100
   libavdevice    57.  7.100 / 57.  7.100
   libavfilter     6. 95.100 /  6. 95.100
   libswscale      4.  7.101 /  4.  7.101
   libswresample   2.  8.100 /  2.  8.100
   libpostproc    54.  6.100 / 54.  6.100
 }}}

 When running a simple h264 1080p 8Mb -> h264 234p ffmpeg quickly overtakes
 1.9GB of 2GB ram before being automagically killed.

 {{{
 Time     Free Mem (MB)
 23:37:36 1747
 23:37:37 1747
 23:37:38 1747
 23:37:39 1684
 23:37:40 1527
 23:37:41 1457
 23:37:42 1309
 23:37:43 1304
 23:37:44 1302
 23:37:45 1301
 23:37:46 1301
 23:37:47 1300
 23:37:48 1300
 23:37:49 1299
 23:37:50 1299
 23:37:51 1298
 23:37:52 1297
 23:37:53 1297
 23:37:54 1297
 23:37:55 1297
 23:37:56 1296
 23:37:57 1296
 23:37:58 1296
 23:37:59 1296
 23:38:00 1296
 23:38:01 1296
 23:38:02 1295
 23:38:03 1295
 23:38:04 1295
 23:38:05 1295
 23:38:06 1295
 23:38:07 1295
 23:38:09 1295
 23:38:10 1294
 23:38:11 1294
 23:38:12 1294
 23:38:13 1294
 23:38:14 1294
 23:38:15 1294
 23:38:16 1294
 23:38:17 1293
 23:38:18 1293
 23:38:19 1293
 23:38:20 1293
 23:38:21 1293
 23:38:22 1293
 23:38:23 1293
 23:38:24 1293
 23:38:25 1293
 23:38:26 1292
 23:38:27 1292
 23:38:28 1292
 23:38:29 1292
 23:38:30 1290
 23:38:31 1289
 23:38:32 1289
 23:38:33 1289
 23:38:34 1289
 23:38:35 1289
 23:38:36 1289
 23:38:37 1289
 23:38:38 1288
 23:38:39 1287
 23:38:40 1285
 23:38:41 1283
 23:38:42 1280
 23:38:43 1278
 23:38:44 1277
 23:38:45 1275
 23:38:46 1272
 23:38:47 1271
 23:38:48 1269
 23:38:49 1268
 23:38:50 1263
 23:38:51 1244
 23:38:52 1105
 23:38:53 1104
 23:38:54 1102
 23:38:55 1099
 23:38:56 923
 23:38:57 622
 23:38:58 351
 23:38:59 332
 23:39:00 313
 23:39:01 312
 23:39:02 313
 23:39:03 312
 23:39:04 312
 23:39:05 312
 23:39:07 312
 23:39:08 312
 23:39:09 312
 23:39:10 311
 23:39:11 311
 23:39:12 311
 23:39:13 311
 23:39:14 311
 23:39:15 311
 23:39:16 311
 23:39:17 311
 23:39:18 310
 23:39:19 310
 23:39:20 310
 23:39:21 310
 23:39:22 310
 23:39:23 310
 23:39:24 310
 23:39:25 310
 23:39:26 310
 23:39:27 309
 23:39:28 309
 23:39:29 309
 23:39:30 309
 23:39:31 309
 23:39:32 309
 23:39:33 309
 23:39:34 309
 23:39:35 309
 23:39:36 309
 23:39:37 308
 23:39:38 308
 23:39:39 308
 23:39:40 308
 23:39:41 308
 23:39:43 308
 23:39:44 308
 23:39:45 308
 23:39:46 308
 23:39:47 308
 23:39:48 308
 23:39:49 307
 23:39:50 307
 23:39:51 307
 23:39:52 307
 23:39:53 307
 23:39:54 307
 23:39:55 307
 23:39:56 306
 23:39:57 306
 23:39:58 306
 23:39:59 306
 23:40:00 306
 23:40:01 305
 23:40:02 305
 23:40:03 305
 23:40:04 305
 23:40:05 305
 23:40:06 305
 23:40:07 304
 23:40:08 303
 23:40:09 301
 23:40:10 301
 23:40:11 76
 23:40:12 40
 23:40:13 27
 23:40:14 27
 23:40:15 26
 23:40:16 26
 23:40:17 26
 23:40:18 26
 23:40:19 25
 23:40:20 25
 23:40:21 24
 23:40:22 23
 23:40:23 23
 23:40:24 22
 23:40:25 22
 23:40:26 22
 23:40:27 0
 23:40:28 0
 23:40:29 0
 23:40:30 0
 23:40:31 0
 23:40:32 0
 23:40:33 0
 23:40:34 0
 23:40:35 0
 23:40:36 0
 23:40:37 0
 23:40:38 0
 23:40:39 0
 23:40:40 0
 23:40:41 0
 23:40:42 1887
 23:40:43 1886
 23:40:44 1886
 23:40:45 1886
 23:40:46 1886
 23:40:47 1886
 23:40:48 1886
 23:40:50 1886
 23:40:51 1886
 23:40:52 1885
 23:40:53 1886
 23:40:54 1885
 23:40:55 1885
 23:40:56 1885
 23:40:57 1885
 }}}

--
Ticket URL: <https://trac.ffmpeg.org/ticket/6530>
FFmpeg <https://ffmpeg.org>
FFmpeg issue tracker


More information about the FFmpeg-trac mailing list