Opened 2 months ago

Last modified 2 months ago

#7500 new defect

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 2 months ago.

Download all attachments as: .zip

Change History (7)

comment:1 Changed 2 months ago by tinybug

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

Last edited 2 months ago by tinybug (previous) (diff)

comment:2 follow-up: Changed 2 months ago by Cigaes

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

Changed 2 months ago by tinybug

comment:3 in reply to: ↑ 2 Changed 2 months ago by tinybug

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 Changed 2 months ago by tinybug

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 Changed 2 months ago by cehoyos

  • 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 Changed 2 months ago by 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 -
Note: See TracTickets for help on using tickets.