Chrome in headless mode failed after window.print()
Reported by
john.doe...@gmail.com,
Jun 22 2017
|
|||||
Issue descriptionUserAgent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/59.0.3071.104 Safari/537.36 Steps to reproduce the problem: 1. Start page with script that consist: let win = window.open(url); win.print(); Where url can be 'https://google.com' 2. Start selenium tests in headless mode. What is the expected behavior? Test should not failed What went wrong? During testing I see folow error in console: [Facebook\WebDriver\Exception\UnknownServerException] chrome not reachable (Session info: headless chrome=59.0.3071.104) (Driver info: chromedriver=2.29,platform=Linux 4.11.3-1-ARCH x86_64) (WARNING: The server did not provide any stacktrace information) Command duration or timeout: 6 milliseconds Build info: version: '3.4.0', revision: 'unknown', time: 'unknown' System info: host: 'localhost', ip: '127.0.0.1', os.name: 'Linux', os.arch: 'amd64', os.version: '4.11.3-1-ARCH', java.version: '1.8.0_131' Driver info: org.openqa.selenium.chrome.ChromeDriver Capabilities [{applicationCacheEnabled=false, rotatable=false, mobileEmulationEnabled=false, networkConnectionEnabled=false, chrome={chromedriverVersion=2.29, userDataDir=/tmp/.org.chromium.Chromium.728tu6}, takesHeapSnapshot=true, pageLoadStrategy=normal, databaseEnabled=false, handlesAlerts=true, hasTouchScreen=false, version=59.0.3071.104, platform=LINUX, browserConnectionEnabled=false, nativeEvents=true, acceptSslCerts=true, locationContextEnabled=true, webStorageEnabled=true, browserName=chrome, takesScreenshot=true, javascriptEnabled=true, cssSelectorsEnabled=true, unexpectedAlertBehaviour=}] Session ID: 5d06184c4ef6e78af13983da29ed078f Did this work before? No Chrome version: 59.0.3071.104 Channel: stable OS Version: Linux 4.11.3-1-ARCH Flash Version: Selenium: 3.4.0 Test framework: PHP Codeception PHP 7.1.6
,
Jul 17 2017
,
Jul 18 2017
,
Jul 25 2017
I can't reproduce this on M61. Is this only a problem on M59?
,
Jul 26 2017
Could not reproduce in version: Version 59.0.3071.115 (Developer Build) (64-bit)
,
Jul 26
This issue has been Available for over a year. If it's no longer important or seems unlikely to be fixed, please consider closing it out. If it is important, please re-triage the issue. Sorry for the inconvenience if the bug really should have been left as Available. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot |
|||||
►
Sign in to add a comment |
|||||
Comment 1 by ranjitkan@chromium.org
, Jun 29 2017