What steps will reproduce the problem?
1.Publish WebRTC stream from Chrome to another peer.
2.Receive PLI from the peer.
3.

What is the expected result?
Chrome should form RTCP packet with K-frame


What do you see instead?
Chrome ignores PLI, does not reply with K-frame and uses internal fixed GOP instead.


What version of the product are you using? On what operating system?
Windows 8, 64 bit
Windows 8.1, 64 bit
Chrome 59.0.3071.86 (Official Build) (64-bit)


Please provide any additional information below.
The same issue is not reproduced with Windows 7.
On Win7 Chrome reacts properly on PLI and sends K-frame.

This is what we see on Windows 8 in Chrome debug logs:

[7924:11200:0613/190921.746:VERBOSE1:rtcp_receiver.cc(959)] Incoming PLI from SSRC 1214065284

and no further reaction 

This is what we see on Windows 7 in the same version of Chrome:

[9996:10160:0613/154402.674:VERBOSE1:rtcp_receiver.cc(959)] Incoming PLI from SSRC 1930031941
[9996:9292:0613/154402.695:INFO:sps_vui_rewriter.cc(273)] VUI bitstream already contains an optimal VUI
[9996:9292:0613/154403.494:INFO:vie_encoder.cc(130)] Number of frames: captured 1773, dropped (due to encoder blocked) 1, interval_ms 60000
[9996:6148:0613/154403.507:WARNING:video_receive_stream.cc(487)] No decodable frame in 3000 ms, requesting keyframe.

So on Windows 7 we have a prompt reaction on PLI request and we are able to see that K-frame is received and assembled on our receiver peer (Web Call Server 5).