Repro steps:
1. Connect to a chromoting host from HP Chromebook (chell)
Connection stalls shortly after (as reported in chrome://webrtc-internals/ ). Screen stops updating, while the host keeps sending video. It appears that the problem is on the receiver side, particularly with video decoding. I see the following logs:
[1:26:1208/164259:WARNING:packet_buffer.cc(145)] PacketBuffer is already at max size (2048), failed to increase size.
[1:26:1208/164259:WARNING:packet_buffer.cc(145)] PacketBuffer is already at max size (2048), failed to increase size.
[1:41:1208/164259:WARNING:nack_module.cc(245)] Sequence number 39773 removed from NACK list due to max retries.
[1:41:1208/164259:WARNING:nack_module.cc(245)] Sequence number 39774 removed from NACK list due to max retries.
[1:41:1208/164259:WARNING:nack_module.cc(245)] Sequence number 39775 removed from NACK list due to max retries.
[1:41:1208/164259:WARNING:nack_module.cc(245)] Sequence number 39776 removed from NACK list due to max retries.
[1:41:1208/164259:WARNING:nack_module.cc(245)] Sequence number 39777 removed from NACK list due to max retries.
[1:41:1208/164259:WARNING:nack_module.cc(245)] Sequence number 39778 removed from NACK list due to max retries.
[1:41:1208/164259:WARNING:nack_module.cc(245)] Sequence number 39780 removed from NACK list due to max retries.
[1:41:1208/164259:WARNING:nack_module.cc(245)] Sequence number 39782 removed from NACK list due to max retries.
[1:41:1208/164259:WARNING:nack_module.cc(245)] Sequence number 39785 removed from NACK list due to max retries.
[1:26:1208/164259:WARNING:packet_buffer.cc(145)] PacketBuffer is already at max size (2048), failed to increase size.
[1:26:1208/164259:WARNING:packet_buffer.cc(145)] PacketBuffer is already at max size (2048), failed to increase size.
[1:26:1208/164259:WARNING:packet_buffer.cc(145)] PacketBuffer is already at max size (2048), failed to increase size.
[1:26:1208/164259:WARNING:packet_buffer.cc(145)] PacketBuffer is already at max size (2048), failed to increase size.
Comment 1 by sergeyu@chromium.org
, Dec 9 2016