[FFmpeg-trac] #5764(undetermined:closed): ffmpeg deadlock with first pass x264 encode with >=slower and bitrate set
FFmpeg
trac at avcodec.org
Thu Aug 11 14:51:43 EEST 2016
#5764: ffmpeg deadlock with first pass x264 encode with >=slower and bitrate set
-------------------------------------+-------------------------------------
Reporter: MonoS | Owner:
Type: defect | Status: closed
Priority: important | Component:
Version: git-master | undetermined
Keywords: | Resolution:
Blocking: | worksforme
Analyzed by developer: 0 | Blocked By:
| Reproduced by developer: 0
-------------------------------------+-------------------------------------
Comment (by MonoS):
Sorry for my lack of knowledge, i've compiled ffmpeg from the latest git
with my usual environment [i did not turned off optimization], downloaded
gdb and tried doing as in your documentation here
https://ffmpeg.org/bugreports.html but i don't know how to have the
backtrace when the process get stuck.
Then tried attaching the process and printing a backtrace but i only got
this
{{{
#0 0x00007ff909fa21e1 in ntdll!DbgUiContinue ()
from C:\Windows\SYSTEM32\ntdll.dll
#1 0x00007ff909fcf3a4 in ntdll!EtwEventActivityIdControl ()
from C:\Windows\SYSTEM32\ntdll.dll
#2 0x0000000000000000 in ?? ()
}}}
Instead, this is the info all-register dump
{{{
rax 0x7ff5ffe8c000
rbx 0x7ff909fcf370
rxc 0x0
rdx 0x7ff909fcf370
rsp 0x428aff28
rip 0x7ff909fa21e1 (ntdll!DbgUiContinue+1)
eflags 0x246 [PF ZF IF]
cs 0x33
ss 0x246002b
gs 0x2b0000
fctrl 0x27f
}}}
the other register are empty [0x0]
I'm sure i'm doing something wrong with gdb, if i may have some more
extensive instruction i'll provide all the information i can.
I don't think it may be an hardware issue, i've tried it on 4 different
machine with the same results
--
Ticket URL: <https://trac.ffmpeg.org/ticket/5764#comment:2>
FFmpeg <https://ffmpeg.org>
FFmpeg issue tracker
More information about the FFmpeg-trac
mailing list