Crash of Chrome when open Settings Tab
Reported by
tmarb...@gmail.com,
Dec 19 2016
|
||||||||
Issue descriptionUserAgent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/55.0.2883.87 Safari/537.36 Steps to reproduce the problem: 1. Open Browser 2. Click on "Customize and control Google Chrome" 3. Clich on Settings What is the expected behavior? Open Settings Tab What went wrong? Crash of Chrome without an Error message Crashed report ID: 46cc42aa-22fa-407b-93ba-e9c2dc776ab8 How much crashed? Whole browser Is it a problem with a plugin? N/A Did this work before? N/A Chrome version: 55.0.2883.87 Channel: stable OS Version: 10.0 Flash Version: Shockwave Flash 24.0 r0
,
Dec 21 2016
tmarbi70@ could you please provide the server ID of this crash which is located in "chrome://crashes" Attaching screen-cast for your reference
,
Dec 21 2016
kkaluri@ thank for the response. Unfortunately the crash history I have deleted from my PC. But I have a new one from yesterday Crash-ID ddddcb47-efc3-49a1-a0b5-14d3ba48597c (Server-ID: c5eb6e4080000000) But every time Chrome crashes on the settings page a new crash without server id is generated Crash-ID e983a2ed-6e71-42aa-aa84-e8488651dda6
,
Dec 21 2016
kkaluri@ thank for the response. Unfortunately the crash history I have deleted from my PC. But I have a new one from yesterday Crash-ID ddddcb47-efc3-49a1-a0b5-14d3ba48597c (Server-ID: c5eb6e4080000000) But every time Chrome crashes on the settings page a new crash without server id is generated Crash-ID e983a2ed-6e71-42aa-aa84-e8488651dda6 2016-12-21 11:04 GMT+01:00 kkal… via monorail < monorail+v2.2099402154@chromium.org>:
,
Dec 28 2016
Thank you for providing more feedback. Adding requester "kkaluri@chromium.org" for another review and adding "Needs-Review" label for tracking. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
Jan 24 2017
Stack Trace: ------------ Thread 17 CRASHED [EXCEPTION_ACCESS_VIOLATION_READ @ 0x00000000 ] MAGIC SIGNATURE THREAD Stack Quality76%Show frame trust levels 0x0000000180001a33 (GcamFilter64.dll + 0x00001a33 ) 0x00000001800054a3 (GcamFilter64.dll + 0x000054a3 ) 0x0000000180011741 (GcamFilter64.dll + 0x00011741 ) 0x00007fffe80e53ee (chrome.dll -video_capture_device_factory_win.cc:327 ) media::GetDeviceSupportedFormatsDirectShow 0x00007fffe73ef53f (chrome.dll -video_capture_manager.cc:1042 ) content::VideoCaptureManager::ConsolidateDevicesInfoOnDeviceThread(base::Callback<void ,1,1>,std::vector<content::VideoCaptureManager::DeviceInfo,std::allocator<content::VideoCaptureManager::DeviceInfo> > const &,std::unique_ptr<std::list<media::VideoCaptureDeviceDescriptor,std::allocator<media::VideoCaptureDeviceDescriptor> >,std::default_delete<std::list<media::VideoCaptureDeviceDescriptor,std::allocator<media::VideoCaptureDeviceDescriptor> > > >) 0x00007fffe73f17e3 (chrome.dll -bind_internal.h:339 ) base::internal::Invoker<base::internal::BindState<void ( content::VideoCaptureManager::*)(base::Callback<void ,1,1>,std::vector<content::VideoCaptureManager::DeviceInfo,std::allocator<content::VideoCaptureManager::DeviceInfo> > const &,std::unique_ptr<std::list<media::VideoCaptureDeviceDescriptor,std::allocator<media::VideoCaptureDeviceDescriptor> >,std::default_delete<std::list<media::VideoCaptureDeviceDescriptor,std::allocator<media::VideoCaptureDeviceDescriptor> > > >),scoped_refptr<content::VideoCaptureManager>,base::Callback<void ,1,1>,std::vector<content::VideoCaptureManager::DeviceInfo,std::allocator<content::VideoCaptureManager::DeviceInfo> > >,void >::Run(base::internal::BindStateBase *,std::unique_ptr<std::list<media::VideoCaptureDeviceDescriptor,std::allocator<media::VideoCaptureDeviceDescriptor> >,std::default_delete<std::list<media::VideoCaptureDeviceDescriptor,std::allocator<media::VideoCaptureDeviceDescriptor> > > > &&) 0x00007fffe80dfa45 (chrome.dll -video_capture_device_factory.cc:55 ) media::VideoCaptureDeviceFactory::EnumerateDeviceDescriptors(base::Callback<void ,1,1> const &) 0x00007fffe7853003 (chrome.dll -task_annotator.cc:54 ) base::debug::TaskAnnotator::RunTask(char const *,base::PendingTask const &) 0x00007fffe77f0c84 (chrome.dll -message_loop.cc:405 ) base::MessageLoop::RunTask(base::PendingTask const &) 0x00007fffe77f1904 (chrome.dll -message_loop.cc:513 ) base::MessageLoop::DoWork() 0x00007fffe78538d0 (chrome.dll -message_pump_win.cc:263 ) base::MessagePumpForUI::DoRunLoop() 0x00007fffe78535a3 (chrome.dll -message_pump_win.cc:141 ) base::MessagePumpWin::Run(base::MessagePump::Delegate *) 0x00007fffe78380fc (chrome.dll -run_loop.cc:35 ) base::RunLoop::Run() 0x00007fffe7817b1b (chrome.dll -thread.cc:333 ) base::Thread::ThreadMain() 0x00007fffe77e4f6c (chrome.dll -platform_thread_win.cc:84 ) base::`anonymous namespace'::ThreadFunc 0x00007ff816618101 (KERNEL32.DLL + 0x00018101 ) BaseThreadInitThunk 0x00007ff81872c5b3 (ntdll.dll + 0x0005c5b3 ) RtlUserThreadStart This issue first seen on #52.0.2743.116, Below link gives in details of the number of instances in which the crash has occurred for associated builds: https://crash.corp.google.com/browse?q=product.name%3D%27Chrome%27%20%20AND%20custom_data.ChromeCrashProto.ptype%3D%27browser%27%20AND%20custom_data.ChromeCrashProto.magic_signature_1.name%3D%27%5BThird%20party%20-%20gcamfilter64.dll%5D%20media%3A%3AGetDeviceSupportedFormatsDirectShow%27&ignore_case=false&enable_rewrite=true&omit_field_name=&omit_field_value=&omit_field_opt=%3D Note: ===== 1) This is a browser crash listed under Stable build 55.0.2883.87 for Windows OS. 2) Observing 12 crash instances on 7 different client ID's 3) No crashes observed on latest beta, dev and canary channels. Last crash is observed on 56.0.2894.0 with 2 instances Used code search for the file "video_capture_device_factory_win.cc" and suspecting the below change Review URL: https://codereview.chromium.org/2169013002 chfremer@: Could you please check if this is caused with respect to your change, if not please help us in reassign the issue to the right owner. Thanks!
,
Mar 14 2017
This looks like a crash in a webcam driver. I am marking this as blocked on issue 584797 since the best we can hope to do is prevent the crash from bringing down the whole browser.
,
May 19 2017
Users experienced this crash on the following builds: Win Canary 60.0.3104.0 - 1.00 CPM, 6 reports, 2 clients (signature [Third party - gcamfilter64.dll] media::GetDeviceSupportedFormatsDirectShow) If this update was incorrect, please add "Fracas-Wrong" label to prevent future updates. - Go/Fracas
,
Jul 6
Crash analysis has not encountered any reports for this bug for the past 90 days. We have added the label 'crash-BugNoRepro' Crash analysis will be automatically closing the bug in 10 days. If you do not want Crash analysis to automatically close the bug, please remove the label 'crash-BugNoRepro'. If you have any feedback on this feature, please contact pranavk@
,
Jul 16
Crash analysis has not encountered any reports for this bug for the past 90 days. Hence as per the comment 10 days ago, we are closing the bug and setting the status to WontFix. If you have any feedback on this feature, please contact pranavk@ |
||||||||
►
Sign in to add a comment |
||||||||
Comment 1 by ajha@chromium.org
, Dec 20 2016