Styjun

What does this sign on a hiking trail communicate?

Why did the VIC-II and SID use 6 µm technology in the era of 3 µm and 1.5 µm?

How do I stop making people jump at home and at work?

Are manifolds admitting a circle foliation covered by manifolds with a (non-trivial) circle action?

Do we know the problems the University of Manchester's Transistor Computer was intended to solve?

What is the maximal acceptable delay between pilot's input and flight control surface actuation?

Unkown DIP IC (OP277PA)

Is mathematics truth?

Calculus Books, preferably Soviet.

Received email from ISP saying one of my devices has malware

Heuristic argument for the Riemann Hypothesis

'Hard work never hurt anyone' Why not 'hurts'?

How to check status of Wi-Fi adapter through command line?

Declaring 2 (or even multi-) dimensional std::arrays elegantly

In mathematics is there a substitution that is "different" from Vieta's substitution to solve the cubic equation?

IEEE Registration Authority mac prefix

Some questions about Lightning and Tor

Is torque as fundamental a concept as force?

How Total raw is calculated for Science pack 2?

What is the converted mana cost of land cards?

Does secure hashing imply secure symmetric encryption?

How to use multiple criteria for -find

One hour 10 min layover in Newark; International -> Domestic connection. Enough time to clear customs?

Solve this icositetragram

Chrome 73 stop supporting headless mode in background scheduled task?

Why does my karma-config.js triggers multiple launches of karma, with only the first working?Best way to run scheduled tasksCatch tasks from windows task scheduler in a .net appRun a task every x-minutes with Windows Task Schedulerdoes windows have a limitation when a process started by a scheduled task under one set of creds runs another program under a different set of CredsAdding a Schedule Task Module for WPF Window ApplicationWindows Task Scheduler reports incorrect/inconsistent result codeDisable Task Scheduler headless (silent) modeWindows 10 - Task Scheduler - Not running (0x41303)Run a scheduled task with ChromeDriverChrome Headless Doesn't work

.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty margin-bottom:0;

2

2

We have a .NET program to run headless Chrome to snapshot web page to image, and here is the sample code:

class Program

 static void Main(string[] args)
 
 var p = Process.Start(
 @"C:Program Files (x86)GoogleChromeApplicationchrome.exe",
 $@"--headless --screenshot=E:testDateTime.Now:HHmmss.png --disable-gpu --window-size=320,568 http://www.microsoft.com");
 p.WaitForExit();
 

The console application is scheduled in Windows Task Scheduler with "Run whether user is logged on or not" option. The program works fine for months but failed yesterday, we noticed the Chrome version is 73 now. Luckily we found a computer in which Chrome is still 72, so we tested the background scheduled task once, upgraded Chrome to 73 and tested it again, finally got the conclusion - Headless Chrome 72 can run in background, but Chrome 73 can't.

Does anybody find the same issue on Chrome 73?

[updated on 2019/6/23]

It's a bug of Chromium (bug 942023) and has been fixed on Chrome 74.0.3729.108.

For Chrome 73, you can use --disable-features=VizDisplayCompositor argument as a workaround.

scheduled-tasks google-chrome-headless

share|improve this question

edited Jun 23 at 8:23

Darkthread

asked Mar 28 at 1:46

DarkthreadDarkthread

1,57933 gold badges1313 silver badges6060 bronze badges

add a comment | 

2

2

We have a .NET program to run headless Chrome to snapshot web page to image, and here is the sample code:

class Program

 static void Main(string[] args)
 
 var p = Process.Start(
 @"C:Program Files (x86)GoogleChromeApplicationchrome.exe",
 $@"--headless --screenshot=E:testDateTime.Now:HHmmss.png --disable-gpu --window-size=320,568 http://www.microsoft.com");
 p.WaitForExit();
 

The console application is scheduled in Windows Task Scheduler with "Run whether user is logged on or not" option. The program works fine for months but failed yesterday, we noticed the Chrome version is 73 now. Luckily we found a computer in which Chrome is still 72, so we tested the background scheduled task once, upgraded Chrome to 73 and tested it again, finally got the conclusion - Headless Chrome 72 can run in background, but Chrome 73 can't.

Does anybody find the same issue on Chrome 73?

[updated on 2019/6/23]

It's a bug of Chromium (bug 942023) and has been fixed on Chrome 74.0.3729.108.

For Chrome 73, you can use --disable-features=VizDisplayCompositor argument as a workaround.

scheduled-tasks google-chrome-headless

share|improve this question

edited Jun 23 at 8:23

Darkthread

asked Mar 28 at 1:46

DarkthreadDarkthread

1,57933 gold badges1313 silver badges6060 bronze badges

add a comment | 

We have a .NET program to run headless Chrome to snapshot web page to image, and here is the sample code:

class Program

 static void Main(string[] args)
 
 var p = Process.Start(
 @"C:Program Files (x86)GoogleChromeApplicationchrome.exe",
 $@"--headless --screenshot=E:testDateTime.Now:HHmmss.png --disable-gpu --window-size=320,568 http://www.microsoft.com");
 p.WaitForExit();
 

The console application is scheduled in Windows Task Scheduler with "Run whether user is logged on or not" option. The program works fine for months but failed yesterday, we noticed the Chrome version is 73 now. Luckily we found a computer in which Chrome is still 72, so we tested the background scheduled task once, upgraded Chrome to 73 and tested it again, finally got the conclusion - Headless Chrome 72 can run in background, but Chrome 73 can't.

Does anybody find the same issue on Chrome 73?

[updated on 2019/6/23]

It's a bug of Chromium (bug 942023) and has been fixed on Chrome 74.0.3729.108.

For Chrome 73, you can use --disable-features=VizDisplayCompositor argument as a workaround.

scheduled-tasks google-chrome-headless

share|improve this question

edited Jun 23 at 8:23

Darkthread

asked Mar 28 at 1:46

DarkthreadDarkthread

1,57933 gold badges1313 silver badges6060 bronze badges

class Program

 static void Main(string[] args)
 
 var p = Process.Start(
 @"C:Program Files (x86)GoogleChromeApplicationchrome.exe",
 $@"--headless --screenshot=E:testDateTime.Now:HHmmss.png --disable-gpu --window-size=320,568 http://www.microsoft.com");
 p.WaitForExit();
 

share|improve this question

edited Jun 23 at 8:23

Darkthread

asked Mar 28 at 1:46

DarkthreadDarkthread

1,57933 gold badges1313 silver badges6060 bronze badges

share|improve this question

edited Jun 23 at 8:23

Darkthread

asked Mar 28 at 1:46

DarkthreadDarkthread

1,57933 gold badges1313 silver badges6060 bronze badges

asked Mar 28 at 1:46

DarkthreadDarkthread

1,57933 gold badges1313 silver badges6060 bronze badges

asked Mar 28 at 1:46

DarkthreadDarkthread

1,57933 gold badges1313 silver badges6060 bronze badges

1 Answer
1

active

oldest

votes

4

Yes, we have the same issue here. We're running Chrome through Selenium WebDriver and after the update to Chrome 73 our background tasks no longer function correctly. Downgrading to Chrome 72 fixes the problem.

Our diagnostics logs show that when running Chrome 73 in headless mode that certain calls to the Chrome process seem to hang. For instance, resizing the browser or trying to take a screenshot via the WebDriver API. We tried a number of things to fix this including updating Selenium, WebDriver and chromedriver to the latest versions but all had identical behaviours.

There certainly seems to be an issue with running Chrome 73 in headless mode after the update.

share|improve this answer

edited Mar 28 at 13:03

answered Mar 28 at 12:57

Mark SmithMark Smith

4122 bronze badges

• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  Thanks for confirming this issue.
  
  – Darkthread
  Mar 29 at 9:18
  

  
  
  
  

add a comment | 

Your Answer

StackExchange.ifUsing("editor", function ()
StackExchange.using("externalEditor", function ()
StackExchange.using("snippets", function ()
StackExchange.snippets.init();
);
);
, "code-snippets");

StackExchange.ready(function()
var channelOptions =
tags: "".split(" "),
id: "1"
;
initTagRenderer("".split(" "), "".split(" "), channelOptions);

StackExchange.using("externalEditor", function()
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled)
StackExchange.using("snippets", function()
createEditor();
);

else
createEditor();

);

function createEditor()
StackExchange.prepareEditor(
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader:
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
,
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
);



);

draft saved

draft discarded

Sign up or log in

StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);

Sign up using Google

Sign up using Facebook

Sign up using Email and Password

Post as a guest

Name

Email

Required, but never shown

StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f55388995%2fchrome-73-stop-supporting-headless-mode-in-background-scheduled-task%23new-answer', 'question_page');

);

Post as a guest

Name

Email

Required, but never shown

4

Yes, we have the same issue here. We're running Chrome through Selenium WebDriver and after the update to Chrome 73 our background tasks no longer function correctly. Downgrading to Chrome 72 fixes the problem.

Our diagnostics logs show that when running Chrome 73 in headless mode that certain calls to the Chrome process seem to hang. For instance, resizing the browser or trying to take a screenshot via the WebDriver API. We tried a number of things to fix this including updating Selenium, WebDriver and chromedriver to the latest versions but all had identical behaviours.

There certainly seems to be an issue with running Chrome 73 in headless mode after the update.

share|improve this answer

edited Mar 28 at 13:03

answered Mar 28 at 12:57

Mark SmithMark Smith

4122 bronze badges

• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  Thanks for confirming this issue.
  
  – Darkthread
  Mar 29 at 9:18
  

  
  
  
  

add a comment | 

4

Yes, we have the same issue here. We're running Chrome through Selenium WebDriver and after the update to Chrome 73 our background tasks no longer function correctly. Downgrading to Chrome 72 fixes the problem.

Our diagnostics logs show that when running Chrome 73 in headless mode that certain calls to the Chrome process seem to hang. For instance, resizing the browser or trying to take a screenshot via the WebDriver API. We tried a number of things to fix this including updating Selenium, WebDriver and chromedriver to the latest versions but all had identical behaviours.

There certainly seems to be an issue with running Chrome 73 in headless mode after the update.

share|improve this answer

edited Mar 28 at 13:03

answered Mar 28 at 12:57

Mark SmithMark Smith

4122 bronze badges

• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  Thanks for confirming this issue.
  
  – Darkthread
  Mar 29 at 9:18
  

  
  
  
  

add a comment | 

Yes, we have the same issue here. We're running Chrome through Selenium WebDriver and after the update to Chrome 73 our background tasks no longer function correctly. Downgrading to Chrome 72 fixes the problem.

Our diagnostics logs show that when running Chrome 73 in headless mode that certain calls to the Chrome process seem to hang. For instance, resizing the browser or trying to take a screenshot via the WebDriver API. We tried a number of things to fix this including updating Selenium, WebDriver and chromedriver to the latest versions but all had identical behaviours.

There certainly seems to be an issue with running Chrome 73 in headless mode after the update.

share|improve this answer

edited Mar 28 at 13:03

answered Mar 28 at 12:57

Mark SmithMark Smith

4122 bronze badges

share|improve this answer

edited Mar 28 at 13:03

answered Mar 28 at 12:57

Mark SmithMark Smith

4122 bronze badges

answered Mar 28 at 12:57

Mark SmithMark Smith

4122 bronze badges

answered Mar 28 at 12:57

Mark SmithMark Smith

4122 bronze badges