New issue
Advanced search Search tips

Issue 842333 link

Starred by 2 users
Status: WontFix
Owner:
jcliang@chromium.org
Closed: May 2018
Cc:
hiroh@chromium.org
jcliang@chromium.org
posciak@chromium.org
tfiga@chromium.org
vsu...@chromium.org
henryhsu@chromium.org
hywu@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 1
Type: Bug-Regression



Sign in to add a comment

Chrome crash while running apprtc video in loop

Project Member Reported by avkodipelli@chromium.org, May 11 2018 
Chrome Version: 68.0.3425.0
Chrome OS Version: 10666.0.0 
Chrome OS Platform: Nautilus
Network info: Wifi

Please specify Cr-* of the system to which this bug/feature applies (add
the label below).

Steps To Reproduce:
(1) Run http://apprtc.appspot.com/?debug=loopback&vsc=h264 to run apprtc call in loop.
(2)  Observe system behavior
(3)

Expected Result:
-- No chrome crash

Actual Result:
-- Chrome crash observed

How frequently does this problem reproduce? (Always, sometimes, hard to
reproduce?)
Always.

feedback report: 85432396141

Crash Id: dfbe4e19561bb3b5, 8967f8f58ace654c
93769d7b1ae2c0e3 ,  9c7b3f1af3066e80

Comment 1 by terelius@chromium.org, May 14 2018

Components: -Blink>WebRTC>Video -OS>Kernel>Audio OS>Kernel>Camera OS>Kernel>Video
Only one of the crash ids (93769d7b1ae2c0e3) contains a stack trace and that stack trace seems to identify a Nautilus specific camera driver. I don't see anything related to WebRTC or kernel audio, so I'm removing those tags. Please add them back if I'm missing something.

I suggest that the ChromeOS team triages this issue.

Comment 2 by conradlo@chromium.org, May 14 2018

Cc: jcliang@chromium.org
Owner: tfiga@chromium.org
+tfiga, jcliang based on feedback from comment #1

Comment 3 by tfiga@chromium.org, May 17 2018

Cc: hywu@chromium.org tfiga@chromium.org henryhsu@chromium.org
Owner: jcliang@chromium.org
The report mentioned in #1 refers to media::CameraHalDispatcherImpl::StartServiceLoop, which isn't a driver, but a part of Chrome Video Capture Device I believe. Ricky, could you triage?

Comment 4 by posciak@chromium.org, May 17 2018

Cc: hiroh@chromium.org

Comment 5 by jcliang@chromium.org, May 17 2018 

I can't reproduce it on my Nautilus with the same image version.

Comment 6 by jcliang@chromium.org, May 17 2018 

From the crash report of 93769d7b1ae2c0e3 indicates that the crash was actaully due to a SIGABRT in the browser main thread:

Thread 0 (id: 1400) CRASHED [SIGABRT @ 0x000003e800000551 ]
Stack Quality99%Show frame trust levels
0x00007a80ef2681ff	(libpthread-2.23.so + 0x0000d1ff )	pthread_cond_wait
0x00005cf9bcffedc3	(chrome -condition_variable_posix.cc:71 )	base::WaitableEvent::TimedWaitUntil(base::TimeTicks const&)
0x00005cf9bf735699	(chrome -waitable_event_posix.cc:154 )	base::internal::TaskTracker::PerformShutdown()
0x00005cf9bf734972	(chrome -task_tracker.cc:274 )	base::internal::TaskSchedulerImpl::Shutdown()
0x00005cf9bdba33b5	(chrome -browser_main_loop.cc:1088 )	content::BrowserMainLoop::ShutdownThreadsAndCleanUp()
0x00005cf9bdba5abd	(chrome -browser_main_runner.cc:215 )	content::BrowserMainRunnerImpl::Shutdown()
0x00005cf9bdb9bc74	(chrome -browser_main.cc:48 )	content::BrowserMain(content::MainFunctionParams const&)
0x00005cf9bf36ae7a	(chrome -content_main_runner.cc:640 )	content::ContentMainRunnerImpl::Run()
0x00005cf9bf375d32	(chrome -main.cc:452 )	service_manager::Main(service_manager::MainParams const&)
0x00005cf9bd0b1e07	(chrome -content_main.cc:19 )	ChromeMain
0x00007a80ee316735	(libc-2.23.so -libc-start.c:289 )	__libc_start_main
0x00005cf9bd0a4b08	(chrome + 0x00295b08 )	_start
0x00007ffee0af5327		

The stack trace for media::CameraHalDispatcherImpl::StartServiceLoop looks like red herring.

Comment 7 by jcliang@chromium.org, May 17 2018

Status: WontFix (was: Untriaged)
Closing this one as WontFix. Please re-open if the issue still exist in other image version.
►

Sign in to add a comment