New issue
Advanced search Search tips

Issue 704886 link

Starred by 6 users

Issue metadata

Status: WontFix
Owner:
Closed: May 2017
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Windows
Pri: 1
Type: Bug-Regression



Sign in to add a comment

Crash: [Renderer hang] content::ResourceDispatcher::StartSync

Project Member Reported by sheriffbot@chromium.org, Mar 24 2017

Issue description

Crash Signature: [Renderer hang] content::ResourceDispatcher::StartSync
Process Type: Renderer
Platform: Win
Channel: Beta
Version: 58.0.3029.33
Distinct Clients: 101
CPM: 0.60
Crash Reports: 105
Median Uptime: 11m:53s
Infected Clients: 6.67%

Sample Reports:
https://crash.corp.google.com/browse?q=reportid=%2737eacd5480000000%27
https://crash.corp.google.com/browse?q=reportid=%2757e23e4b60000000%27
https://crash.corp.google.com/browse?q=reportid=%275ad05b7960000000%27
https://crash.corp.google.com/browse?q=reportid=%27858d81a960000000%27
https://crash.corp.google.com/browse?q=reportid=%27f858235480000000%27

Crash Link:
https://crash.corp.google.com/browse?q=product.name%3D%27Chrome%27%20AND%20product.version%3D%2758.0.3029.33%27%20AND%20custom_data.ChromeCrashProto.magic_signature_1.name%3D%27%5BRenderer%20hang%5D%20content%3A%3AResourceDispatcher%3A%3AStartSync%27

Crash Link (with version impact distribution):
https://crash.corp.google.com/browse?q=product.name%3D%27Chrome%27%20AND%20custom_data.ChromeCrashProto.magic_signature_1.name%3D%27%5BRenderer%20hang%5D%20content%3A%3AResourceDispatcher%3A%3AStartSync%27

Crash Stacktrace:
0x0517a7ed (0x7fff3283d163)
#0 0x7fff4270217a in NtWaitForAlertByThreadId 
#1 0x7fff426ee65b in RtlSleepConditionVariableSRW 
#2 0x7fff3fb68da7 in SleepConditionVariableSRW 
#3 0x7fff10bc1394 in base::ConditionVariable::Wait base/synchronization/condition_variable_win.cc:26
#4 0x7fff10d71b02 in mojo::edk::Core::WaitManyInternal mojo/edk/system/core.cc:1148
#5 0x7fff10d718d1 in mojo::edk::Core::Wait mojo/edk/system/core.cc:395
#6 0x7fff10d71db5 in MojoWaitImpl mojo/edk/embedder/entrypoints.cc:35
#7 0x7fff10d71ce0 in mojo::SyncHandleRegistry::WatchAllHandles mojo/public/cpp/bindings/lib/sync_handle_registry.cc:75
#8 0x7fff10ee2edb in IPC::SyncChannel::WaitForReply ipc/ipc_sync_channel.cc:620
#9 0x7fff10de0f20 in IPC::SyncChannel::Send ipc/ipc_sync_channel.cc:584
#10 0x7fff10de0de4 in content::RenderThreadImpl::Send content/renderer/render_thread_impl.cc:951
#11 0x7fff10d89fab in content::ResourceDispatchThrottler::Send content/renderer/scheduler/resource_dispatch_throttler.cc:54
#12 0x7fff113472ce in content::ResourceDispatcher::StartSync content/child/resource_dispatcher.cc:630
#13 0x7fff10ebaf5d in content::WebURLLoaderImpl::Context::Start content/child/web_url_loader_impl.cc:624
#14 0x7fff11348484 in content::WebURLLoaderImpl::loadSynchronously content/child/web_url_loader_impl.cc:1204
#15 0x7fff113482f4 in blink::ResourceLoader::requestSynchronously third_party/webkit/source/platform/loader/fetch/resourceloader.cpp:472
#16 0x7fff10b9d02d in blink::ResourceLoader::start third_party/webkit/source/platform/loader/fetch/resourceloader.cpp:102
#17 0x7fff10b9d29f in blink::ResourceFetcher::startLoad third_party/webkit/source/platform/loader/fetch/resourcefetcher.cpp:1278
#18 0x7fff10eb7f91 in blink::ResourceFetcher::requestResource third_party/webkit/source/platform/loader/fetch/resourcefetcher.cpp:625
#19 0x7fff1105d1f5 in blink::RawResource::fetchSynchronously third_party/webkit/source/platform/loader/fetch/rawresource.cpp:41
#20 0x7fff1105cf23 in blink::DocumentThreadableLoader::loadRequestSync third_party/webkit/source/core/loader/documentthreadableloader.cpp:1046
#21 0x7fff10dc1ce1 in blink::DocumentThreadableLoader::loadRequest third_party/webkit/source/core/loader/documentthreadableloader.cpp:1124
#22 0x7fff10dc1948 in blink::DocumentThreadableLoader::dispatchInitialRequest third_party/webkit/source/core/loader/documentthreadableloader.cpp:300
#23 0x7fff10dc1861 in blink::DocumentThreadableLoader::start third_party/webkit/source/core/loader/documentthreadableloader.cpp:292
#24 0x7fff110d9144 in blink::ThreadableLoader::loadResourceSynchronously third_party/webkit/source/core/loader/threadableloader.cpp:72
#25 0x7fff10dc1534 in blink::XMLHttpRequest::createRequest third_party/webkit/source/core/xmlhttprequest/xmlhttprequest.cpp:1066
#26 0x7fff10dc0f9b in blink::XMLHttpRequest::send third_party/webkit/source/core/xmlhttprequest/xmlhttprequest.cpp:810
#27 0x7fff10dc0f26 in blink::XMLHttpRequest::send third_party/webkit/source/core/xmlhttprequest/xmlhttprequest.cpp:752
#28 0x7fff10dc0e58 in blink::XMLHttpRequestV8Internal::sendMethod out/release_x64/gen/blink/bindings/core/v8/v8xmlhttprequest.cpp:381
#29 0x7fff10b4ebdf in v8::internal::`anonymous namespace'::HandleApiCallHelper<0> v8/src/builtins/builtins-api.cc:111
#30 0x7fff10b5048c in v8::internal::Builtin_Impl_HandleApiCall v8/src/builtins/builtins-api.cc:140
#31 0x7fff10b503b1 in v8::internal::Builtin_HandleApiCall v8/src/builtins/builtins-api.cc:128
#33 0x7fff10a757df in v8::internal::StoreIC::UpdateCaches v8/src/ic/ic.cc:1831


Reporter: beherad

 
Cc: -beherad@google.com tzik@chromium.org
Components: Blink>Loader
Labels: -Type-Bug M-57 OS-Windows Type-Bug-Regression
Status: Assigned (was: Untriaged)
Looking at the historical data it looks spiked in M56, and its a top # 19 (render hang) crash not a renderer crash as per updates on  Issue 545179 .
59.0.3039.0	0.00%	1	--M59
58.0.3029.33	0.00%	1	--M58(dev)

57.0.2987.110	0.91%	1706	--M57 Stable(1%)
57.0.2987.98	1.87%	3515	
57.0.2987.88	0.01%	17	

56.0.2924.87	94.69%	177712	--M56
56.0.2924.76	1.92%	3609	

55.0.2883.87	0.35%	653	--M55
55.0.2883.75	0.01%	21	

Link to list of builds:
https://goto.google.com/uluyh
Possible suspect: Review-Url: https://codereview.chromium.org/2390983003
tzik@: Could you please take a look into this if its related to your change.
Not adding any blocker its regressed in M56.
Project Member

Comment 2 by sheriffbot@chromium.org, Mar 24 2017

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

Win Beta 58.0.3029.33 -  0.55 CPM, 109 reports, 104 clients (signature [Renderer hang] content::ResourceDispatcher::StartSync)

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

- Go/Fracas
Status: Untriaged (was: Assigned)
Moving back items w/o OWNERs to untriaged

Comment 4 by japhet@chromium.org, May 10 2017

Labels: -Restrict-View-EditIssue
Owner: japhet@chromium.org
Status: WontFix (was: Untriaged)
This looks like just another stack for the classic sync request hang: a sync XHR on the main thread never gets a response and hangs the main thread. See issues  331909 ,  545179 , etc.
Issue 776502 has been merged into this issue.
Issue 830571 has been merged into this issue.
Issue 836794 has been merged into this issue.
Issue 836795 has been merged into this issue.
Issue 837218 has been merged into this issue.
Cc: pnangunoori@chromium.org
Labels: FoundIn-67
Just to update the latest behavior of this issue in the latest channels:

Still seeing 481 crashes from 430 clients so far on latest Stable - 67.0.3396.99 on Windows OS. This crash is ranked as number #30 in 'Extension' Stable crashes. 

Link to the list of builds:
-------------------------
https://crash.corp.google.com/browse?q=product_name%3D%27Chrome%27+AND+expanded_custom_data.ChromeCrashProto.channel%3D%27%27+AND+expanded_custom_data.ChromeCrashProto.ptype%3D%27extension%27+AND+expanded_custom_data.ChromeCrashProto.magic_signature_1.name%3D%27%5BRenderer+hang%5D+content%3A%3AResourceDispatcher%3A%3AStartSync%27#-productname:1000,productversion:100,-magicsignature:50,-magicsignature2:50,-stablesignature:50,-magicsignaturesorted:50

japhet@ -- Could you please look into the crashes are the instance are still seen on latest #67.0.3396.99.

Thanks!

Sign in to add a comment