New issue
Advanced search Search tips
Note: Color blocks (like █ or █) mean that a user may not be available. Tooltip shows the reason.

Issue 591214 link

Starred by 1 user
Status: WontFix
Owner: ----
Closed: Mar 2016
Cc:
█ tnakamura@chromium.org
avkodipelli@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 2
Type: Bug



Sign in to add a comment

Device Pi hangs up during WebRTC tests

Project Member Reported by srcv@chromium.org, Mar 1 2016 
Chrome Version: 50.0.2661.1 / 7978.1.0 dev 
Device: Pi

Crash IDs related to system hangs:
a)Crash ID 54b08e9800000000 (Chrome)
b)Crash ID 91cf9ea000000000 (Chrome)
c)Crash ID 7822bf2000000000 (Chrome)
d)Crash ID 9627972000000000 (Chrome)

What steps will reproduce the problem?

1.Browse to https://test.webrtc.org/ 
2. Click Allow in the getUserMedia prompt
3. Click Start
4. Observe that systems gets stuck and only mouse cursor movements are working.

Expected result:
Tests should complete successfully

Actual result:
System is hanging up. Sometimes system hang is seen as soon as any tab is opened , sometimes after opening up some webrtc pages and sometimes while checking emails on the device.



Please see attached generate_logs dump from device Pi
log-030116-151702.tar.gz
1.0 MB Download

Comment 1 by srcv@chromium.org, Mar 4 2016 

Observed system hang on device Pi with today's M50 dev build 50.0.2661.11 / 7978.4.0 while running WebRTC tests as mentioned in initial bug report.

Crash ID: 4950643400000000 
Please find attached generate_logs from device Pi.
log-030316-162632.tar.gz
1.1 MB Download

Comment 2 by srcv@chromium.org, Mar 16 2016

Status: WontFix (was: Untriaged)
Performed WebRTC tests on device Pi with M50 version 50.0.2661.32 / 7978.18.0 dev and verified that tests completed successfully. No system hangs are observed.
►

Sign in to add a comment