New issue
Advanced search Search tips

Issue 788082 link

Starred by 1 user

Issue metadata

Status: WontFix
Owner: ----
Closed: Dec 2017
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 2
Type: Bug-Regression



Sign in to add a comment

Webrtc page not responding while record and playback long video (more than 1 hour).

Issue description

UserAgent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/62.0.3202.94 Safari/537.36
Platform: 10144.0.0-17.11.19

Steps to reproduce the problem:
1. Open chrome browser and enter WebRTC samples link. https://webrtc.github.io/samples/
2. Launch “Record stream”.
3. Start recording for overnight or more than 1 hour.
4. Stop recording.
5. Click on Play button to check the recorded audio and video.

What is the expected behavior?
Webrtc should play recorded video

What went wrong?
Webrtc page unresponsive error observed while record and playback long video (more than 1 hour)

Crashed report ID: 

How much crashed? Just one tab

Is it a problem with a plugin? N/A 

Did this work before? Yes Chrome 63.0.3236.0

Chrome version:  64.0.3272.0  Channel: n/a
OS Version: R64.10122.0.0
Flash Version: 

Issue is reproducible on Reef and Soraka
 
Electro & Soraka_logs.zip
3.3 MB Download
Labels: Proj-Poppy
Cc: emir...@chromium.org niklase@chromium.org
Components: Blink>WebRTC
Cc: conradlo@chromium.org

Comment 4 by guidou@chromium.org, Nov 27 2017

Components: -Blink>WebRTC Blink>MediaRecording
Cc: chfremer@chromium.org

Comment 6 by chfremer@google.com, Nov 27 2017

Please let me know if you disagree, but I think this is expected behavior.
The media recorder sample collects blobs from the recorder in the JavaScript environment. This naturally only works for a limited amount of data until the memory limit is reached.

In order to enable longer recordings, the JavaScript app would have to push the data it obtains out of memory, e.g. by uploading it to some server, in regular intervals before the memory limit is reached.
According to Jenny:

Seems like it regressed between 10026 to 10078. 10026 was the last version in which we verified the scenario.


Did this work before? Yes Chrome 63.0.3236.0


Cc: mcasas@chromium.org
Here is the diff for reference. I didn't come across to a mediarecorder related change in it though.
https://chromium.googlesource.com/chromium/src/+log/63.0.3236.0..64.0.3253.0?pretty=fuller&n=10000
Status: WontFix (was: Unconfirmed)
The sample page isn't designed to handle long recordings.

Sign in to add a comment