Crash when navigating between chrome://safe-browsing pages
Reported by
daveyy.k...@gmail.com,
Nov 12 2017
|
||||||
Issue descriptionUserAgent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/64.0.3260.2 Safari/537.36 Steps to reproduce the problem: 1. Navigate to a chrome://safe-browsing page (e.g. chrome://safe-browsing/match?type=malware) 2. Navigate to any other chrome://safe-browsing page (e.g. chrome://safe-browsing/match?type=phishing) What is the expected behavior? Chrome navigates to the new chrome://safe-browsing page as normal What went wrong? Whole browser crash Crashed report ID: 95434940-85dc-4350-9630-f5a608f9d666 How much crashed? Whole browser Is it a problem with a plugin? No Did this work before? N/A Chrome version: 64.0.3260.2 Channel: dev OS Version: 10.0 Flash Version: 27.0.0.187 Tested with these 3 pages and navigating between any of causes a whole browser crash: chrome://safe-browsing/match?type=malware chrome://safe-browsing/match?type=phishing chrome://safe-browsing/match?type=unwanted
,
Nov 14 2017
Ah, before I do that I noticed you navigated using a different tab. Try repeating the steps but do the navigation using the same tab?
,
Nov 14 2017
Thank you for providing more feedback. Adding requester "hdodda@chromium.org" to the cc list and removing "Needs-Feedback" label. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
Nov 15 2017
Thanks for the update. We tried navigating the urls from the same tab and still we are unable to reproduce the crash in windows 10 & 7 using chrome dev M64 #64.0.3260.2. Attached screencast for reference. @daveyy.king-- Could you please check in a fresh profile without any extensiona and flags enabled and update us with your observations. Also help us in proividng the complete crash id along with reporter id from chrome://crashes. Thanks!
,
Nov 15 2017
So I can't reproduce it in a fresh profile or incognito mode but I disabled all extensions in my profile and it still occurs, maybe it's a flag causing the issue. Crash Report ID 883f0b4c6c806296 (Local Crash ID: dea88072-60a2-4e17-8f35-d0f7fdac00a9)
,
Nov 15 2017
Thank you for providing more feedback. Adding requester "hdodda@chromium.org" to the cc list and removing "Needs-Feedback" label. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
Nov 20 2017
Thanks for the update! Could you please enable all your flags in your profile and provide the chrome://version page which would help us to triage the issue further. Stack trace for the provided crash id: -------------------------------------- Thread 0 CrBrowserMain (id: 884) CRASHED [EXCEPTION_BREAKPOINT @ 0x00007ffc777a28c2 ] MAGIC SIGNATURE THREAD Stack Quality100%Show frame trust levels 0x00007ffc777a28c2 (chrome.dll -web_ui_message_handler.cc:23 ) content::WebUIMessageHandler::AllowJavascript() 0x00007ffc788086f7 (chrome.dll -safe_browsing_ui.cc:378 ) safe_browsing::SafeBrowsingUIHandler::NotifyThreatDetailsJsListener(safe_browsing::ClientSafeBrowsingReportRequest *) 0x00007ffc78808692 (chrome.dll -safe_browsing_ui.cc:50 ) safe_browsing::WebUIInfoSingleton::AddToReportsSent(std::unique_ptr<safe_browsing::ClientSafeBrowsingReportRequest,std::default_delete<safe_browsing::ClientSafeBrowsingReportRequest> >) 0x00007ffc78be9626 (chrome.dll -bind_internal.h:311 ) base::internal::Invoker<base::internal::BindState<void (sync_file_system::drive_backend::SyncWorkerInterface::*)(std::unique_ptr<sync_file_system::drive_backend::SyncEngineContext,std::default_delete<sync_file_system::drive_backend::SyncEngineContext> >),base::internal::UnretainedWrapper<sync_file_system::drive_backend::SyncWorkerInterface>,base::internal::PassedWrapper<std::unique_ptr<sync_file_system::drive_backend::SyncEngineContext,std::default_delete<sync_file_system::drive_backend::SyncEngineContext> > > >,void ()>::RunOnce 0x00007ffc76d0d616 (chrome.dll -task_annotator.cc:55 ) base::debug::TaskAnnotator::RunTask(char const *,base::PendingTask *) 0x00007ffc76d0d10b (chrome.dll -message_loop.cc:394 ) base::MessageLoop::RunTask(base::PendingTask *) 0x00007ffc76d0ce86 (chrome.dll -message_loop.cc:457 ) base::MessageLoop::DoWork() 0x00007ffc76dce77c (chrome.dll -message_pump_win.cc:173 ) base::MessagePumpForUI::DoRunLoop() 0x00007ffc76d19bd4 (chrome.dll -message_pump_win.cc:56 ) base::MessagePumpWin::Run(base::MessagePump::Delegate *) 0x00007ffc76d0c9d3 (chrome.dll -run_loop.cc:114 ) base::RunLoop::Run() 0x00007ffc76ff01a3 (chrome.dll -chrome_browser_main.cc:1919 ) ChromeBrowserMainParts::MainMessageLoopRun(int *) 0x00007ffc76feff9a (chrome.dll -browser_main_loop.cc:1201 ) content::BrowserMainLoop::RunMainMessageLoopParts() 0x00007ffc76feff48 (chrome.dll -browser_main_runner.cc:140 ) content::BrowserMainRunnerImpl::Run() 0x00007ffc76d06b42 (chrome.dll -browser_main.cc:46 ) content::BrowserMain(content::MainFunctionParams const &) 0x00007ffc76d06989 (chrome.dll -content_main_runner.cc:427 ) content::RunNamedProcessTypeMain(std::basic_string<char,std::char_traits<char>,std::allocator<char> > const &,content::MainFunctionParams const &,content::ContentMainDelegate *) 0x00007ffc76d04639 (chrome.dll -content_main_runner.cc:705 ) content::ContentMainRunnerImpl::Run() 0x00007ffc76cf4eaf (chrome.dll -main.cc:456 ) service_manager::Main(service_manager::MainParams const &) 0x00007ffc76cf4a45 (chrome.dll -content_main.cc:19 ) content::ContentMain(content::ContentMainParams const &) 0x00007ffc76cf2320 (chrome.dll -chrome_main.cc:123 ) ChromeMain 0x00007ff60d9f34f9 (chrome.exe -main_dll_loader_win.cc:199 ) MainDllLoader::Launch(HINSTANCE__ *,base::TimeTicks) 0x00007ff60d9f169c (chrome.exe -chrome_exe_main_win.cc:230 ) wWinMain 0x00007ff60dacb572 (chrome.exe -exe_common.inl:283 ) __scrt_common_main_seh 0x00007ffcaa901fe3 (KERNEL32.DLL + 0x00011fe3 ) BaseThreadInitThunk 0x00007ffcac98ef90 (ntdll.dll + 0x0006ef90 ) RtlUserThreadStart Adding dev for further inputs. @lukasza: This stack trace is similar to issue 780920. it is fixed in M63. Could you please look in to this issue. Thank You!
,
Nov 20 2017
The fix for issue 780920 has initially landed in 64.0.3264.0 (and was later merged into M63 - 63.0.3239.50). Looking at crash data today, I don't see any crashes for WebUIMessageHandler::AllowJavascript after 64.0.3264. I also see that this bug was opened against an earlier version that didn't yet include the fix (64.0.3260.2). So - I think it is safe to resolve the current bug as a duplicate of issue 780920. Please reopen the bug if you can repro the crash in 64.0.3264.0 or later version. |
||||||
►
Sign in to add a comment |
||||||
Comment 1 by hdodda@chromium.org
, Nov 14 2017Labels: Needs-Feedback
526 KB
526 KB View Download