New issue
Advanced search Search tips

Issue 909039 link

Starred by 3 users

Issue metadata

Status: Duplicate
Owner: ----
Closed: Dec 4
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Linux , Windows , Mac
Pri: 2
Type: Bug

Blocking:
issue chromedriver:2660



Sign in to add a comment

Renderer process crashes when page is redirected in popup controlled by ChromeDriver

Project Member Reported by johnchen@chromium.org, Nov 27

Issue description

Chrome Version: 70.0.3538.110 and above
OS: Win10, MacOS 10.14.1, Linux

What steps will reproduce the problem?
(1) Run the attached Python script repro.py. (ChromeDriver and Selenium Python API need to be installed.)

What is the expected result?
The script finishes without any errors.

What happens instead?
The script hangs during the call to driver.current_url. This used to work in Chrome 69. Bisecting shows this issue started with r584254.

Further investigation indicates that a Chrome renderer process has crashed. Here is the crash call stack:

[1:1:1127/142945.154088:FATAL:window_proxy.cc(105)] Check failed: global_proxy_.IsEmpty(). 
#0 0x55c699d942cf base::debug::StackTrace::StackTrace()
#1 0x55c699d0a330 logging::LogMessage::~LogMessage()
#2 0x55c69c4388c4 blink::WindowProxy::SetGlobalProxy()
#3 0x55c69c8d7fe7 blink::WindowProxyManager::SetGlobalProxies()
#4 0x55c69ca0fa2b blink::WebFrame::Swap()
#5 0x55c69d3b5a69 content::RenderFrameImpl::SwapIn()
#6 0x55c69d3c0fbb content::RenderFrameImpl::DidCommitProvisionalLoad()
#7 0x55c69cb0032c blink::LocalFrameClientImpl::DispatchDidCommitLoad()
#8 0x55c69ceea96c blink::DocumentLoader::DidCommitNavigation()
#9 0x55c69cee9cb6 blink::DocumentLoader::InstallNewDocument()
#10 0x55c69cee99a8 blink::DocumentLoader::CommitNavigation()
#11 0x55c69cee8b46 blink::DocumentLoader::CommitData()
#12 0x55c69ceea022 blink::DocumentLoader::ProcessData()
#13 0x55c69cee9edf blink::DocumentLoader::DataReceived()
#14 0x55c69960f04f blink::Resource::NotifyDataReceived()
#15 0x55c69960ed40 blink::Resource::AppendData()
#16 0x55c69962dcc7 blink::ResourceLoader::DidReceiveData()
#17 0x55c69d6e4cd1 content::WebURLLoaderImpl::Context::OnReceivedData()
#18 0x55c69d6e52da content::WebURLLoaderImpl::RequestPeerImpl::OnReceivedData()
#19 0x55c69d3969eb content::URLResponseBodyConsumer::OnReadable()
#20 0x55c69d395178 content::URLLoaderClientImpl::FlushDeferredMessages()
#21 0x55c699d0fe68 base::debug::TaskAnnotator::RunTask()
#22 0x55c699d4f7df base::sequence_manager::internal::ThreadControllerImpl::DoWork()
#23 0x55c699d0fe68 base::debug::TaskAnnotator::RunTask()
#24 0x55c699d0f3ff base::MessageLoopImpl::RunTask()
#25 0x55c699d0f922 base::MessageLoopImpl::DoWork()
#26 0x55c699d114da base::MessagePumpDefault::Run()
#27 0x55c699d2d825 base::RunLoop::Run()
#28 0x55c69dc32636 content::RendererMain()
#29 0x55c699967267 content::RunZygote()
#30 0x55c6999683dd content::ContentMainRunnerImpl::Run()
#31 0x55c6999999c6 service_manager::Main()
#32 0x55c699966871 content::ContentMain()
#33 0x55c697a3b1b3 ChromeMain
#34 0x7f8913d0f2b1 __libc_start_main
#35 0x55c697a3b02a _start

The ChromeDriver log is attached, and contains more information at the time of crash.

What seems to trigger the hang is opening a popup window using a URL that immediately redirects. The crash is only observed when the browser is controlled by ChromeDriver, not when the same action is done manually.
 
repro.py
410 bytes View Download
chromedriver.log
30.8 KB View Download
Cc: alex...@chromium.org dcheng@chromium.org
+dcheng@ and alexmos@ who know how to extract the real callstack that is responsible for the crash here.
Cc: dgozman@chromium.org
Components: -Blink Platform>DevTools
Speculatively adding Platform>DevTools component, since AFAIR there were some recent bugs and fixes related to DevTools / SetGlobalProxy interaction.
I haven't tried the repro, but this could be related to issue 897816.
Mergedinto: 897816
Status: Duplicate (was: Untriaged)
Hello! This issue is linked with chromedriver issue. Can you please make https://bugs.chromium.org/p/chromium/issues/detail?id=897816 issue not private so it'll be possible to track progress. This issue heavily affects selenium testing under chrome.
alph@chromium.org, lukasza@chromium.org,  johnchen@chromium.org, are there any updates? It's not possible to track progress in linked issue as it's not visible due to some permissions.

Sign in to add a comment