Opened 4 years ago

Closed 10 months 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)

WechatIMG447.png (44.7 KB ) - added by tinybug 4 years ago.

Download all attachments as: .zip

Change History (9)

comment:1 by tinybug, 4 years ago

The test.jpg is 8.9M, I can't upload. The resolution of test.jpg is 6000x4000.

Last edited 4 years ago by tinybug (previous) (diff)

comment:2 by Nicolas George, 4 years ago

Does the problem happen only with this particular JPEG file or does it happen with any file of a similar resolution?

by tinybug, 4 years ago

Attachment: WechatIMG447.png added

in reply to:  2 comment:3 by tinybug, 4 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 tinybug, 4 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 Carl Eugen Hoyos, 4 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.

comment:6 by Carl Eugen Hoyos, 4 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 -

in reply to:  6 comment:7 by Balling, 3 years ago

Status: newopen

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
Last edited 3 years ago by Balling (previous) (diff)

comment:8 by Elon Musk, 10 months ago

Resolution: invalid
Status: openclosed
Note: See TracTickets for help on using tickets.