Opened 6 years ago
Closed 3 years ago
#7500 closed defect (invalid)
memory leak
Reported by: | tinybug | Owned by: | |
---|---|---|---|
Priority: | normal | Component: | undetermined |
Version: | git-master | Keywords: | libx264 |
Cc: | Blocked By: | ||
Blocking: | Reproduced by developer: | no | |
Analyzed by developer: | no |
Description
It's use too much memory by this command:
ffmpeg -loop 1 -i test.jpg -y test.mp4
Attachments (1)
Change History (9)
follow-up: 3 comment:2 by , 6 years ago
Does the problem happen only with this particular JPEG file or does it happen with any file of a similar resolution?
by , 6 years ago
Attachment: | WechatIMG447.png added |
---|
comment:3 by , 6 years ago
it happen with any file of a similar resolution.
Replying to Cigaes:
Does the problem happen only with this particular JPEG file or does it happen with any file of a similar resolution?
comment:4 by , 6 years ago
I have uploaded the test.jpg to Dropbox, https://www.dropbox.com/s/k6z7do2rgkkabsu/test.jpg.zip?dl=0, you can download from here.
comment:5 by , 6 years ago
Keywords: | libx264 added; memory leak removed |
---|
Not an obvious regression, I doubt that it is a leak and I suspect it cannot be fixed in FFmpeg.
follow-up: 7 comment:6 by , 6 years ago
If there is an issue, it can be reproduced with the following command line:
$ ffmpeg -benchmark -f lavfi -i testsrc2=s=6000x4000,format=yuv422p -vcodec libx264 -f null -
comment:7 by , 4 years ago
Status: | new → open |
---|
Replying to cehoyos:
If there is an issue, it can be reproduced with the following command line:
$ ffmpeg -benchmark -f lavfi -i testsrc2=s=6000x4000,format=yuv422p -vcodec libx264 -f null -
Well there is indeed 5 Gb of memory used. Cannot say if it is a memory leak, it is not growing. It is just immediately 5 Gb. I used that one
ffmpeg -loop 1 -i test.jpg -y test.mp4
comment:8 by , 3 years ago
Resolution: | → invalid |
---|---|
Status: | open → closed |
The test.jpg is 8.9M, I can't upload. The resolution of test.jpg is 6000x4000.