[GH-ISSUE #804] [BUG] exec.Command with FFMPEG uses a lot of memory #1410

New issue

Closed

opened 2026-03-07 22:09:18 +03:00 by kerem · 1 comment

kerem commented

2026-03-07 22:09:18 +03:00

Owner

Originally created by @jhemmmm on GitHub (Jan 12, 2024).
Original GitHub issue: https://github.com/hibiken/asynq/issues/804

Originally assigned to: @hibiken on GitHub.

Describe the bug
I am currently using exec.Command to run a ffmpeg to transcode a video. For some reason, the size of the video is being opened in the memory. For example, if you have a 10GB video file, my asynq server will have a 10GB memory.

Originally created by @jhemmmm on GitHub (Jan 12, 2024). Original GitHub issue: https://github.com/hibiken/asynq/issues/804 Originally assigned to: @hibiken on GitHub. **Describe the bug** I am currently using exec.Command to run a ffmpeg to transcode a video. For some reason, the size of the video is being opened in the memory. For example, if you have a 10GB video file, my asynq server will have a 10GB memory.

kerem

2026-03-07 22:09:18 +03:00

closed this issue
added the
bug

invalid
labels

kerem commented

2026-03-07 22:09:19 +03:00

Author

Owner

@kamikazechaser commented on GitHub (Jan 28, 2024):

This is not related to asynq. Review your handler implementation to take care of what it does.

@kamikazechaser commented on GitHub (Jan 28, 2024): This is not related to asynq. Review your handler implementation to take care of what it does.

No milestone

No project

No assignees

1 participant

Notifications

Due date

The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference

starred/asynq#1410

No description provided.

Rows
Columns