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

Issue 597088 link

Starred by 1 user
Status: WontFix
Owner:
niklase@chromium.org
Closed: Apr 2016
Cc:
mflodman@chromium.org
sprang@chromium.org
█ tnakamura@chromium.org
█ srnarayanan@chromium.org
█ brandtr@chromium.org
terelius@chromium.org
holmer@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 1
Type: Bug-Regression



Sign in to add a comment

Regression: Crash seen during WebRTC tests on devices Jerry, Pit

Project Member Reported by srcv@chromium.org, Mar 22 2016 
Chrome Version: 51.0.2686.0 / 8097.0.0 dev
Device: Jerry
Crash ID :  3b52266400000000 , 1335266400000000

What steps will reproduce the problem?
1. Browse to https://test.webrtc.org/ 
2. Click Allow in the getUserMedia prompt
3. Click Start

Expected result:
All tests should pass

Actual result:
Tab crashes with "Aw,Snap! Something went wrong while displaying this webpage"


Notes:
1. Please find attached generate_logs dump from device Jerry
2. This issue is reproduced 3/3 times
3. Crash is also observed as soon as call is initiated on following pages on device Jerry:
a) https://webrtc.github.io/samples/src/content/peerconnection/pc1/ page
b)  https://webrtc.github.io/samples/src/content/peerconnection/pr-answer/
c)  https://webrtc.github.io/samples/src/content/peerconnection/multiple-relay/
log-032216-152838.tar.gz
1.3 MB Download

Comment 1 by tnakamura@chromium.org, Mar 23 2016

Cc: srnarayanan@chromium.org mflodman@chromium.org
Labels: -Pri-2 M-51 Pri-1
Owner: niklase@chromium.org
Status: Assigned (was: Untriaged)
srcv@ - can you confirm that this is a regression relative to M50?
srnarayanan@ - are you seeing any similar crashes on Windows, Mac, or Linux?

Thread 22 CRASHED [SIGSEGV @ 0x00000000 ] MAGIC SIGNATURE THREAD
0xb2cf41dc	(chrome -ref_counted.h:280 )	base::ThreadTaskRunnerHandle::Get
0xb4ee893f	(chrome -rtc_video_encoder.cc:243 )	content::RTCVideoEncoder::Impl::Impl
0xb4ee9f15	(chrome -rtc_video_encoder.cc:635 )	content::RTCVideoEncoder::InitEncode
0xb635d1f9	(chrome -simulcast_encoder_adapter.cc:220 )	webrtc::SimulcastEncoderAdapter::InitEncode
0xb6336061	(chrome -video_encoder.cc:103 )	webrtc::VideoEncoderSoftwareFallbackWrapper::InitEncode
0xb634d117	(chrome -generic_encoder.cc:127 )	webrtc::VCMGenericEncoder::InitEncode
0xb634bdeb	(chrome -codec_database.cc:255 )	webrtc::VCMCodecDataBase::SetSendCodec
0xb6351d5f	(chrome -video_sender.cc:90 )	webrtc::vcm::VideoSender::RegisterSendCodec
0xb633b869	(chrome -vie_encoder.cc:194 )	webrtc::ViEEncoder::SetEncoder
0xb6337c41	(chrome -video_send_stream.cc:534 )	webrtc::internal::VideoSendStream::EncoderProcess
0xb6337d09	(chrome -video_send_stream.cc:504 )	webrtc::internal::VideoSendStream::EncoderThreadFunction
0xb613d43f	(chrome -platform_thread.cc:185 )	rtc::PlatformThread::Run
0xb613d461	(chrome -platform_thread.cc:125 )	rtc::PlatformThread::StartThread
0xb218f6b9	(libpthread-2.19.so -pthread_create.c:311 )	start_thread
0xb213265b	(libc-2.19.so + 0x0009e65b )	clone

mflodman@ and niklase@ - can you help find an appropriate owner for this issue?

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

Summary: Regression: Crash seen during WebRTC tests on device Jerry (was: Crash seen during WebRTC tests on device Jerry)
No crashes were observed during WebRTC tests on device Jerry with M50 beta build
(50.0.2661.32 / 7978.18.0)

Feedback submitted for this issue in M51:
https://feedback.corp.google.com/product/208/neutron?lView=rd&lRSort=1&lROrder=2&lRFilter=1&lReportSearch=user:srcv&lReport=7692388587

Comment 3 by srnarayanan@chromium.org, Mar 23 2016 

I ran into a crash in Win 10 in yesterday's Canary 51.0.2687.0, but don't recollect the repro steps now.
Crash ID: 3102c66400000000

However, the crash trace is different from the one reported above

Comment 4 by tnakamura@chromium.org, Mar 23 2016

Components: -Blink>WebRTC Blink>WebRTC>Video
Labels: -Type-Bug Type-Bug-Regression
srcv@ - thanks for the confirmation! I'm updating the bug type accordingly.

srnarayanan@ - your crash doesn't look related to this bug. I think that crash is being tracked in bug 590856.

Comment 5 by srcv@chromium.org, Mar 23 2016

Summary: Regression: Crash seen during WebRTC tests on devices Jerry, Pit (was: Regression: Crash seen during WebRTC tests on device Jerry)
Observed crashes with similar stack trace(comment #1) on device Pit during WebRTC tests and Hangout calls with M51 dev build  51.0.2686.0 / 8097.0.0 dev

Crash ID : b3de36f400000000

Note: Updated this bug with crashes observed on device Pit as it has the same crash stack trace as observed on device Jerry. Please suggest if this issue has to be filed separately.

Comment 6 by mflodman@chromium.org, Apr 5 2016

Cc: sprang@chromium.org

Comment 7 by srcv@chromium.org, Apr 16 2016 

Tested device Pit with M51 51.0.2704.0 / 8172.1.0 dev and did not observe any crashes during WebRTC tests. I will update this bug after testing jerry with M51 latest build

Comment 8 by srcv@chromium.org, Apr 20 2016

Status: WontFix (was: Assigned)
No crashes were observed on device Jerry with M51 51.0.2704.0 / 8172.4.0 dev build during WebRTC tests.

Closing this bug as "Wont fix" as crashes were not observed in the recent tests.
►

Sign in to add a comment