Ticket #7492: valgrind.log

File valgrind.log, 2.1 KB (added by ofarrnbacher, 8 years ago)

valgrind log

Line 
1==2791== Memcheck, a memory error detector
2==2791== Copyright (C) 2002-2015, and GNU GPL'd, by Julian Seward et al.
3==2791== Using Valgrind-3.11.0 and LibVEX; rerun with -h for copyright info
4==2791== Command: /home/cap/FFmpeg4/ffmpeg_g -threads 0 -report -v 9 -loglevel 99 -y -i e70c2e44a3e3 -filter_complex \ split=1\ [vin]\ ;\ [0:1][0:2]amerge=inputs=2\ [ain]\ ;\ [vin]\ copy\ [vsc]\ ;\ [vsc]\ split=4\ [vps0]\ [vps1]\ [vps2]\ [vps3]\ ;\ [ain]\ asplit=4\ [a0]\ [a1]\ [a2]\ [a3]\ ;\ [vps0]\ scale=1280:720\ [v0]\ ;\ [vps1]\ scale=960:540\ [v1]\ ;\ [vps2]\ scale=1280:720\ [v2]\ ;\ [vps3]\ scale=960:540\ [v3]\ -map [v0] -map [a0] -c:v libx264 -profile:v high -b:v 3000k -maxrate:v 3000k -bufsize:v 6000k -g 50 -pix_fmt yuv420p -c:a libfdk_aac -ar 48000 -ac 2 -b:a 256k -colorspace 1 -movflags faststart 1280x720_hp.mp4 -map [v1] -map [a1] -c:v libx264 -profile:v high -b:v 1500k -maxrate:v 1500k -bufsize:v 3000k -g 50 -pix_fmt yuv420p -c:a libfdk_aac -ar 48000 -ac 2 -b:a 128k -colorspace 1 -movflags faststart 960x540_hp.mp4 -map [v2] -map [a2] -c:v libx264 -profile:v baseline -b:v 4000k -maxrate:v 4000k -bufsize:v 8000k -g 50 -pix_fmt yuv420p -c:a libfdk_aac -ar 48000 -ac 2 -b:a 256k -colorspace 1 -movflags faststart 1280x720_bp.mp4 -map [v3] -map [a3] -c:v libx264 -profile:v baseline -b:v 2000k -maxrate:v 2000k -bufsize:v 4000k -g 50 -pix_fmt yuv420p -c:a libfdk_aac -ar 48000 -ac 2 -b:a 128k -colorspace 1 -movflags faststart 960x540_bp.mp4
5==2791== Parent PID: 2790
6==2791==
7==2791==
8==2791== HEAP SUMMARY:
9==2791== in use at exit: 73,939 bytes in 5 blocks
10==2791== total heap usage: 14,859 allocs, 14,854 frees, 115,726,298 bytes allocated
11==2791==
12==2791== LEAK SUMMARY:
13==2791== definitely lost: 0 bytes in 0 blocks
14==2791== indirectly lost: 0 bytes in 0 blocks
15==2791== possibly lost: 0 bytes in 0 blocks
16==2791== still reachable: 73,939 bytes in 5 blocks
17==2791== suppressed: 0 bytes in 0 blocks
18==2791== Rerun with --leak-check=full to see details of leaked memory
19==2791==
20==2791== For counts of detected and suppressed errors, rerun with: -v
21==2791== ERROR SUMMARY: 0 errors from 0 contexts (suppressed: 0 from 0)