Issue metadata
Sign in to add a comment
|
Apparent memory leak when resizing WebRTC streamed application window
Reported by
skadb...@cyviz.com,
Nov 24 2017
|
||||||||||||||||||||||||
Issue descriptionUserAgent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:56.0) Gecko/20100101 Firefox/56.0 Steps to reproduce the problem: 1. Start a WebRTC stream using chrome.desktopCapture.chooseDesktopMedia from any client computer, selecting a window application. 2. Continuously resize the window of the shared application. What is the expected behavior? The stream restarts the video stream with the new resolution as startup parameters, cleaning up all previous data. What went wrong? As the window is resized and the video stream restarted, the Chrome instance on the receiving side consumes more and more memory. On windows/process explorer, the private bytes increases roughly at the rate of 65MB/s. The working set appears to increase at an exponential rate, ranging from 2MB/s to 50MS/s when my system runs out of memory. Reloading the tab releases all memory back to the system. Did this work before? No Does this work in other browsers? N/A Chrome version: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Application/0.4.0 Chrome/56.0.2924.87 Electron/1.6.7 Safari/537.36 or earlier Channel: stable OS Version: Debian 8 Flash Version: N/A |
|||||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||||
Comment 1 by guidou@chromium.org
, Nov 24 2017Status: Duplicate (was: Unconfirmed)