Opened 6 years ago
Closed 6 years ago
#7492 closed defect (needs_more_info)
ffmpeg crashes when using autothreading (-threads 0)
| Reported by: | ofarrnbacher | Owned by: | |
|---|---|---|---|
| Priority: | normal | Component: | undetermined |
| Version: | unspecified | Keywords: | |
| Cc: | Blocked By: | ||
| Blocking: | Reproduced by developer: | no | |
| Analyzed by developer: | no |
Description
Summary of the bug:
How to reproduce:
% ffmpeg -threads 0 -i input output ffmpeg version n4.0.2 built on Ubuntu 16.04.5 LTS
Results in:
Error while filtering: Cannot allocate memory
11800 Failed to inject frame into filter network: Cannot allocate memory
If I set -threads to e.g. 8 then it works.
Happens everytime on Intel(R) Xeon(R) W-2145 CPU @ 3.70GHz
Does NOT happen on Intel(R) Core(TM) i7-3770 CPU @ 3.40GHz
Attachments (5)
Change History (8)
by , 6 years ago
| Attachment: | ffmpeg-20181011-113543.log added |
|---|
by , 6 years ago
| Attachment: | valgrind.sh added |
|---|
comment:1 by , 6 years ago
You are running out of memory. While in an ideal work it should not crash and there is a bug somewhere thats not checking all failure cases somewhere, the lack of memory will always result in ffmpeg failing eventually, even if cleaner then a crash.
comment:2 by , 6 years ago
Try latest master, because you are probably hitting bug in amerge filter that have been fixed.
comment:3 by , 6 years ago
| Component: | avfilter → undetermined |
|---|---|
| Resolution: | → needs_more_info |
| Status: | new → closed |
- Only current FFmpeg git head is supported
- The title contradicts the log files
- I cannot reproduce different behaviour for different number of threads
Note:
See TracTickets
for help on using tickets.
ffmpeg_g -v 9 -loglevel 99