Chrome: Crash Report - [Shutdown hang] extensions::NativeProcessLauncher::LaunchNativeProcess |
|||||||||||||
Issue descriptionProduct name: Chrome Magic Signature: [Shutdown hang] extensions::NativeProcessLauncher::LaunchNativeProcess Current link: https://crash.corp.google.com/browse?q=product.name%3D'Chrome'%20AND%20product.version%3D'56.0.2924.59'%20AND%20custom_data.ChromeCrashProto.ptype%3D'browser'%20AND%20custom_data.ChromeCrashProto.magic_signature_1.name%3D'%5BShutdown%20hang%5D%20extensions%3A%3ANativeProcessLauncher%3A%3ALaunchNativeProcess'%20AND%20ReportID%3D'7e8dacb080000000'&ignore_case=false&enable_rewrite=true&omit_field_name=&omit_field_value=&omit_field_opt=%3D#3 Search properties: product.name: Chrome product.version: 56.0.2924.59 custom_data.chromecrashproto.ptype: browser custom_data.chromecrashproto.magic_signature_1.name: [Shutdown hang] extensions::NativeProcessLauncher::LaunchNativeProcess reportid: 7e8dacb080000000 Metadata : Product Name: Chrome Product Version: 56.0.2924.59 Report ID: 7e8dacb080000000 Report Time: Fri, 13 Jan 2017 05:53:23 GMT Uptime: 3085000 ms Cumulative Uptime: 0 ms User Email: OS Name: Windows NT OS Version: 6.1.7601 17514 CPU Architecture: amd64 CPU Info: family 6 model 23 stepping 10 Stack Trace ============================= Thread 6 MAGIC SIGNATURE THREAD Stack Quality100%Show frame trust levels 0x77bd135a (ntdll.dll + 0x0005135a ) NtWaitForSingleObject 0x000007fefdc06fad (KERNELBASE.dll + 0x00026fad ) _GSHandlerCheck 0x000007fef08a10da (chrome.dll -native_process_launcher_win.cc:162 ) extensions::NativeProcessLauncher::LaunchNativeProcess(base::CommandLine const &,base::Process *,base::File *,base::File *) 0x000007fef089c236 (chrome.dll -native_process_launcher.cc:201 ) extensions::`anonymous namespace'::NativeProcessLauncherImpl::Core::DoLaunchOnThreadPool 0x000007feef0b7faa (chrome.dll -sequenced_worker_pool.cc:1017 ) base::SequencedWorkerPool::Inner::ThreadLoop(base::SequencedWorkerPool::Worker *) 0x000007feef0b6416 (chrome.dll -sequenced_worker_pool.cc:611 ) base::SequencedWorkerPool::Worker::Run() 0x000007feef0b0dcd (chrome.dll -simple_thread.cc:68 ) base::SimpleThread::ThreadMain() 0x000007feef076e3c (chrome.dll -platform_thread_win.cc:84 ) base::`anonymous namespace'::ThreadFunc 0x77a7652c (kernel32.dll + 0x0001652c ) BaseThreadInitThunk 0x77bac520 (ntdll.dll + 0x0002c520 ) RtlUserThreadStart 1) This is a regression crash seen from 51.0.2704.63 having highest spike on latest stable M55 #55.0.2883.87. 2) Currently its a top # 24 browser crasher having 8 crashes from 7 unique client Ids. 3) Crashes are seen on latest M55, M56 and M57 as below. 57.0.2979.0 0.01% 3 --Latest canary/Dev 56.0.2924.59 0.03% 8 --Latest Beta 55.0.2883.87 27.05% 6463 --Latest stable 4) Link to list of builds where crashes are seen: https://crash.corp.google.com/browse?q=product.name%3D%27Chrome%27%20AND%20custom_data.ChromeCrashProto.ptype%3D%27browser%27%20AND%20custom_data.ChromeCrashProto.magic_signature_1.name%3D%27%5BShutdown%20hang%5D%20extensions%3A%3ANativeProcessLauncher%3A%3ALaunchNativeProcess%27&ignore_case=false&enable_rewrite=true&omit_field_name=&omit_field_value=&omit_field_opt=%3D#samplereports:5,productversion:1000 5) Possible suspect from the code search on the crashed file "native_process_launcher_win.cc" based on recent changes made. Review-Url: https://codereview.chromium.org/1871713002 Another possible suspect Review-Url: https://chromiumcodereview.appspot.com/11048047 dcheng@ : Could you please take a look into this if its related to your change or else please help us in assigning it to the right owner. 6) Crashes mostly seen only on Windows and has more crash instances on latest stable #55.0.2883.87, so adding ReleaseBlock-Stable against M57 to get it fixed before stable push. Please feel free to remove if not appropriate. Thanks...!!
,
Jan 18 2017
Users experienced this crash on the following builds: Win Dev 57.0.2984.0 - 0.13 CPM, 6 reports, 6 clients (signature [Shutdown hang] extensions::NativeProcessLauncher::LaunchNativeProcess) If this update was incorrect, please add "Fracas-Wrong" label to prevent future updates. - Go/Fracas
,
Jan 24 2017
Friendly ping to get an update and further investigation of this. Cc'ing sergeyu@ (chromium//src/chrome/browser/extensions/api/messaging/OWNERS) as well for more inputs.
,
Jan 27 2017
I don't know anything about this code, but it looks like a lot of hangs are detected in ConnectNamedPipe()... maybe there's some conditions that can cause this syscall to take a long time?
,
Jan 30 2017
Gentle Ping.! Current dev build 57.0.2987.13 reported 2 instances and previous dev build 57.0.2987.8 reported more than 16 instances for this crash. Below link gives in detail about the same: https://crash.corp.google.com/browse?q=product.name%3D%27Chrome%27%20AND%20custom_data.ChromeCrashProto.ptype%3D%27browser%27%20AND%20custom_data.ChromeCrashProto.magic_signature_1.name%3D%27%5BShutdown%20hang%5D%20extensions%3A%3ANativeProcessLauncher%3A%3ALaunchNativeProcess%27&ignore_case=false&enable_rewrite=true&omit_field_name=&omit_field_value=&omit_field_opt=%3D#samplereports:5,productversion:1000 @sergeyu: Request you to please take a look into it and provide an update on the same as issue is tagged with a blocker label.
,
Jan 30 2017
Looks like in some cases cmd.exe may fail to start, which then hands the thread. I don't think this needs to block M57 release, as it's not a new issue.
,
Jan 30 2017
,
Mar 10 2017
Users experienced this crash on the following builds: Win Canary 59.0.3036.0 - 0.27 CPM, 4 reports, 4 clients (signature [Shutdown hang] extensions::NativeProcessLauncher::LaunchNativeProcess) If this update was incorrect, please add "Fracas-Wrong" label to prevent future updates. - Go/Fracas
,
Mar 11 2017
Users experienced this crash on the following builds: Win Dev 58.0.3029.14 - 0.28 CPM, 3 reports, 3 clients (signature [Shutdown hang] extensions::NativeProcessLauncher::LaunchNativeProcess) If this update was incorrect, please add "Fracas-Wrong" label to prevent future updates. - Go/Fracas
,
Jun 22 2017
Users experienced this crash on the following builds: Win Beta 60.0.3112.40 - 0.11 CPM, 3 reports, 3 clients (signature [Shutdown hang] extensions::NativeProcessLauncher::LaunchNativeProcess) If this update was incorrect, please add "Fracas-Wrong" label to prevent future updates. - Go/Fracas
,
Jan 22 2018
Just to update: [Shutdown hang] extensions::NativeProcessLauncher::LaunchNativeProcess This is top#17th browser crash on latest beta-65.0.3322.3 & still seeing 20 instances from 13 clients so far. 65.0.3322.3 0.11% 14 -Dev 64.0.3282.99 0.15% 20 -beta 63.0.3239.132 52.97% 6882 -Stable Link to the list builds: ----------------------- https://crash.corp.google.com/browse?q=product.name%3D%27Chrome%27AND%20custom_data.ChromeCrashProto.ptype%3D%27browser%27%20AND%20custom_data.ChromeCrashProto.magic_signature_1.name%3D%27%5BShutdown%20hang%5D%20extensions%3A%3ANativeProcessLauncher%3A%3ALaunchNativeProcess%27&sql_dialect=googlesql&ignore_case=false&enable_rewrite=true&omit_field_name=&omit_field_value=&omit_field_opt=%3D#-property-selector,productversion:1000 Could you please take a look into it. Thanks..!
,
Mar 23 2018
Users experienced this crash on the following builds: Win Canary 67.0.3378.0 - 0.09 CPM, 3 reports, 3 clients (signature [Shutdown hang] extensions::NativeProcessLauncher::LaunchNativeProcess) If this update was incorrect, please add "Fracas-Wrong" label to prevent future updates. - Go/Fracas
,
May 8 2018
Just to update the latest behavior, still crash instances are observed on chrome latest stable, beta and dev channels with below instances. Currently this crash is ranked as number #5 under browser process for windows platform. +---------------+----------+----------+ |CHROME VERSION |INSTANCES |CHANNEL | +-------------- +----------+----------+ |66.0.3359.139 | 3400 | Stable | |67.0.3396.30 | 65 | Beta | |68.0.3418.2 | 8 | Dev | +---------------+----------+----------+ Link to list of the builds: --------------------------- https://crash.corp.google.com/browse?q=product.name%3D%27Chrome%27AND%20custom_data.ChromeCrashProto.ptype%3D%27browser%27%20AND%20custom_data.ChromeCrashProto.magic_signature_1.name%3D%27%5BShutdown%20hang%5D%20extensions%3A%3ANativeProcessLauncher%3A%3ALaunchNativeProcess%27&sql_dialect=googlesql&ignore_case=false&enable_rewrite=true&omit_field_name=&omit_field_value=&omit_field_opt=%3D#-property-selector,productversion:1000 Thanks!
,
Jul 20
Just to update the latest behavior of this issue in the latest channels: Still seeing 12 crashes from 8 clients so far on latest beta - 68.0.3440.68 on Windows OS. This crash is ranked as number #9 in 'Browser' beta crashes. Crash data on recent Beta builds: 68.0.3440.68 1.49% 14 68.0.3440.59 7.33% 69 68.0.3440.42 14.67% 138 68.0.3440.33 5.95% 56 68.0.3440.25 5.42% 51 69.0.3493.3 0.00% 2 - Dev 68.0.3440.68 0.02% 14 - Beta 67.0.3396.99 16.53% 11164 - Stable So far no crashes are observed on Canary. 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%27beta%27+AND+expanded_custom_data.ChromeCrashProto.ptype%3D%27browser%27+AND+expanded_custom_data.ChromeCrashProto.magic_signature_1.name%3D%27%5BShutdown+hang%5D+extensions%3A%3ANativeProcessLauncher%3A%3ALaunchNativeProcess%27#-productname:1000,productversion:100,-magicsignature:50,-magicsignature2:50,-stablesignature:50,-magicsignaturesorted:50 Thanks!
,
Aug 23
|
|||||||||||||
►
Sign in to add a comment |
|||||||||||||
Comment 1 by krajshree@chromium.org
, Jan 13 2017