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

Issue 730937 link

Starred by 3 users

Issue metadata

Status: WontFix
Owner:
Last visit > 30 days ago
Closed: Jun 2017
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Windows
Pri: 1
Type: Bug-Regression



Sign in to add a comment

Chrome: Crash Report - rtc::PlatformThread::Start

Project Member Reported by kavvaru@chromium.org, Jun 8 2017

Issue description

Product name: Chrome
Magic Signature: rtc::PlatformThread::Start

Current link:
https://crash.corp.google.com/browse?q=product.name%3D'Chrome'%20AND%20product.version%3D'60.0.3112.20'%20AND%20custom_data.ChromeCrashProto.channel%3D'dev'%20AND%20custom_data.ChromeCrashProto.ptype%3D'renderer'%20AND%20ReportID%3D'2abc34a9f0000000'%20AND%20custom_data.ChromeCrashProto.magic_signature_1.name%3D'rtc%3A%3APlatformThread%3A%3AStart'&ignore_case=false&enable_rewrite=true&omit_field_name=&omit_field_value=&omit_field_opt=%3D#3


Search properties:
product.name: Chrome
product.version: 60.0.3112.20
custom_data.chromecrashproto.channel: dev
custom_data.chromecrashproto.ptype: renderer
reportid: 2abc34a9f0000000

Metadata :
Product Name: Chrome
Product Version: 60.0.3112.20
Report ID: 2abc34a9f0000000
Report Time: Thu, 08 Jun 2017 00:20:46 GMT
Uptime: 105000 ms
Cumulative Uptime: 0 ms
User Email: 
OS Name: Windows NT
OS Version: 6.1.7601 18229
CPU Architecture: x86
CPU Info: GenuineIntel family 6 model 23 stepping 10

Stack trace
=================
Thread 16 (id: 6268) CRASHED [EXCEPTION_ACCESS_VIOLATION_WRITE @ 0x00000000 ] MAGIC SIGNATURE THREAD
Stack Quality100%Show frame trust levels
0x0f94ff30	(chrome_child.dll -win_util.cc:70 )	base::win::`anonymous namespace'::ForceCrashOnSigAbort
0x0fa858bf	(chrome_child.dll -signal.cpp:516 )	raise
0x0fa7429b	(chrome_child.dll -abort.cpp:64 )	abort
0x10706206	(chrome_child.dll -checks.cc:110 )	rtc::FatalMessage::~FatalMessage()
0x107069c1	(chrome_child.dll -platform_thread.cc:156 )	rtc::PlatformThread::Start()
0x10e8267b	(chrome_child.dll -process_thread_impl.cc:74 )	webrtc::ProcessThreadImpl::Start()
0x10e79ca2	(chrome_child.dll -call.cc:420 )	webrtc::internal::Call::Call(webrtc::Call::Config const &,std::unique_ptr<webrtc::RtpTransportControllerSendInterface,std::default_delete<webrtc::RtpTransportControllerSendInterface> >)
0x10e7a8f4	(chrome_child.dll -call.cc:361 )	webrtc::Call::Create(webrtc::Call::Config const &)
0x10e2a927	(chrome_child.dll -peerconnection.cc:2344 )	webrtc::PeerConnection::CreateCall_w()
0x10e2d543	(chrome_child.dll -messagehandler.h:64 )	rtc::FunctorMessageHandler<void,rtc::MethodFunctor<webrtc::PeerConnection,void ( webrtc::PeerConnection::*)(void),void> >::OnMessage(rtc::Message *)
0x10df3e2a	(chrome_child.dll -thread_wrapper.cc:157 )	jingle_glue::JingleThreadWrapper::Dispatch(rtc::Message *)
0x10df40be	(chrome_child.dll -thread_wrapper.cc:226 )	jingle_glue::JingleThreadWrapper::ProcessPendingSends()
0x0f45bbe1	(chrome_child.dll -bind_internal.h:339 )	base::internal::Invoker<base::internal::BindState<void ( blink::HTMLDocumentParser::*)(void),base::WeakPtr<blink::HTMLDocumentParser> >,void >::Run(base::internal::BindStateBase *)
0x0f3fc686	(chrome_child.dll -task_annotator.cc:59 )	base::debug::TaskAnnotator::RunTask(char const *,base::PendingTask *)
0x0f3f9b34	(chrome_child.dll -message_loop.cc:409 )	base::MessageLoop::RunTask(base::PendingTask *)
0x0f3fc2d3	(chrome_child.dll -message_loop.cc:508 )	base::MessageLoop::DoWork()
0x0f3fa633	(chrome_child.dll -message_pump_default.cc:33 )	base::MessagePumpDefault::Run(base::MessagePump::Delegate *)
0x0f685f8f	(chrome_child.dll -message_loop.cc:360 )	base::MessageLoop::Run()
0x0f685f46	(chrome_child.dll -run_loop.cc:111 )	base::RunLoop::Run()
0x0f685f0d	(chrome_child.dll -thread.cc:255 )	base::Thread::Run(base::RunLoop *)
0x0f685ea0	(chrome_child.dll -thread.cc:338 )	base::Thread::ThreadMain()
0x0f685551	(chrome_child.dll -platform_thread_win.cc:89 )	base::`anonymous namespace'::ThreadFunc
0x76c7ed5b	(kernel32.dll + 0x0004ed5b )	BaseThreadInitThunk
0x77ab37ea	(ntdll.dll + 0x000637ea )	__RtlUserThreadStart
0x77ab37bd	(ntdll.dll + 0x000637bd )	_RtlUserThreadStart

This crash is first started from 56.0.2924.87 and on latest dev seeing 9 from 8 different clients.

61.0.3123.0	0.12%	1	
61.0.3122.0	0.36%	3	
60.0.3112.21	1.31%	11	
60.0.3112.20	1.07%	9	
60.0.3112.11	0.12%	1	
60.0.3112.10	0.12%	1	
59.0.3071.86	7.84%	66	
58.0.3029.110	87.65%	738	
58.0.3029.81	0.12%	1	
57.0.2987.133	1.19%	10	
56.0.2924.87	0.12%	1	


Link to the list of builds
https://crash.corp.google.com/browse?q=product.name%3D%27Chrome%27%20AND%20custom_data.ChromeCrashProto.ptype%3D%27renderer%27%20AND%20custom_data.ChromeCrashProto.magic_signature_1.name%3D%27rtc%3A%3APlatformThread%3A%3AStart%27&ignore_case=false&enable_rewrite=true&omit_field_name=&omit_field_value=&omit_field_opt=%3D#samplereports:5,productversion:1000

From the similar bug 687553 assigning to zhihuang

zhihuang@ Could you please look into this issue if it is related to your change,else please help us in finding the appropriate owner for this issue.

Note::
1.This is top #23 renderer crash on chrome Dev 60.0.3112.20	
2.This is not seeing on latest canary channel.
3. This crash is observed only on windows OS.

Thanks,
 
Project Member

Comment 1 by sheriffbot@chromium.org, Jun 8 2017

Labels: Fracas FoundIn-M-60
Users experienced this crash on the following builds:

Win Dev 60.0.3112.20 -  0.27 CPM, 11 reports, 10 clients (signature rtc::PlatformThread::Start)

If this update was incorrect, please add "Fracas-Wrong" label to prevent future updates.

- Go/Fracas
Status: WontFix (was: Assigned)
The crash is occurring due to a failure to create additional threads. I noticed that there are lots of WebRTC threads already alive, but I don't think it's that we're leaking threads. I checked one of the sites the crash occurred on, and it's using a DailyMotion embedded video player that seems to be creating more and more PeerConnection objects over time, and isn't always closing old ones.

Assuming the other sites are doing similar things, I'd view this as an application bug; if an application continues to create more PeerConnections without closing them, eventually it will run out of threads or memory.
Issue 771078 has been merged into this issue.
Cc: msrchandra@chromium.org pnangunoori@chromium.org
 Issue 774395  has been merged into this issue.
Labels: -Restrict-View-Google
Removing restricted view label. This is just an "RTC_CHECK", no reason to hide it I can see.

Sign in to add a comment