New issue
Advanced search Search tips

Issue 890854 link

Starred by 2 users

Issue metadata

Status: Assigned
Owner:
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Linux , Windows , Mac
Pri: 3
Type: Bug



Sign in to add a comment

Chrome crashes when JavaScript code returns large string from DevTools to ChromeDriver

Project Member Reported by johnchen@chromium.org, Oct 1

Issue description

Chrome Version: 69.0.3497.100
OS: Observed on Linux only

What steps will reproduce the problem?
(1) Install ChromeDriver and Python WebDriver API

(2) Run the following Python script:

from selenium import webdriver
driver = webdriver.Chrome()
driver.execute_script('return new Array(1000*1000*1000).join("0")')

What is the expected result?
A string with about 1 billion characters is returned from Chrome/DevTools to ChromeDriver

What happens instead?
On Linux and Mac, Chrome crashes.
On Windows, the page crashes, showing 'Aw Snap' error, though Chrome stays up.

Note: I discovered this issue while investigating  issue #877105 . Returning a shorter string (e.g., about 100 million characters) crashes ChromeDriver instead of Chrome.
Running the same JavaScript code directly in Chrome's DevTools window results in page crash with 'Aw Snap', not Chrome crash.
Running the same JavaScript code inside HTML file works properly.
 
Labels: Needs-Triage-M69
Cc: viswa.karala@chromium.org
Labels: Triaged-ET TE-NeedsTriageHelp
As per comment# 0, issue requires ChromeDriver and Python WebDriver APi to test and confirm the issue, which is out of scope for TE. Hence adding TE-NeedsTriageHelp label to it and requesting someone from the Dev team have a look at this issue.

Thanks!
Owner: dgozman@chromium.org
Status: Assigned (was: Unconfirmed)
I don't think this is expected to work. Renderer hits the memory limit and crashes. Do you have a usecase, John?
This is related to Google internal bug http://b/112588554, which contains a use case. The original bug reported ChromeDriver crashing for certain result sizes. The ChromeDriver crash has now been fixed, but slightly larger result sizes cause Chrome to crash.
Cc: dgozman@chromium.org
Owner: alph@chromium.org

Sign in to add a comment