Chrome Version : Version 50.0.2661.94 m (64-bit)
Operating systems : Tested on Windows 10 and Debian 8.3
What steps will reproduce the problem?
(1) Start WebRTC video stream
(2) Stop stream
(3) Repeat from (1) without closing tab
What is the expected result?
All resources related to the video stream released at (2) and continued normal operation.
What happens instead?
2-3 chrome threads (not processes) remain active for each repetition, consuming resources until tab is fully closed. Occurs on both sender and receiver. The threads can be monitored from applications like Process Explorer.
The attached ZIP archive contains a small test case which repeatedly starts and stops a video stream using WebRTC. It runs on node.js to provide signaling between sender and receiver. For convenience, the sender and receiver runs in a single frameset, but works the same when running from separate processes or devices.
Comment 1 by fataldev...@gmail.com
, May 9 20166.2 KB
6.2 KB Download