[FFmpeg-trac] #8402(ffmpeg:new): CPU hit 100% when two or three ffmpeg instances transcods webm/vp8

[FFmpeg]

#8402: CPU hit 100% when two or three ffmpeg instances transcods webm/vp8
--------------------------------+----------------------------------
             Reporter:  dchang  |                    Owner:
                 Type:  defect  |                   Status:  new
             Priority:  normal  |                Component:  ffmpeg
              Version:  4.2     |               Resolution:
             Keywords:          |               Blocked By:
             Blocking:          |  Reproduced by developer:  0
Analyzed by developer:  0       |
--------------------------------+----------------------------------

Comment (by dchang):

 I am not sure its load causing this. It seems to me that there is
 something similar to an mutex object locking each others. On Windows 10,
 when two ffmpeg instances transcode for live view (even though transcoding
 and CPU looks normal), you would notice that pictures on the two live view
 moving/stop toggling. This indicates the two instances already started to
 block each others. Adding the third instance, it may run n normal CPU for
 a while. Then suddenly all three instances hit CPU to 100%.

--
Ticket URL: <https://trac.ffmpeg.org/ticket/8402#comment:3>
FFmpeg <https://ffmpeg.org>
FFmpeg issue tracker