Chrome Version: (copy from chrome://version)
OS: (e.g. Win7, OSX 10.9.5, etc...)
What steps will reproduce the problem?
(1) Start logging an RTC event log. Observe the local-id part of the filename.
(2) Create a new file with the same name, except that the local-id is incremented by one.
(3) Start another peer connection on the same renderer.
What is the expected result?
A new file is created.
What happens instead?
Either the existing file is used, or logging doesn't work. I'll check which of these when I get around to fixing this.
Please use labels and text to provide additional information.
For graphics-related bugs, please copy/paste the contents of the about:gpu
page at the end of this report.
Comment 1 by eladalon@chromium.org
, Nov 9 2017