Light House script halts before completion
Reported by
rkoll...@nisum.com,
Oct 24
|
|||||
Issue descriptionChrome Version : Google Chrome 69.0.3497.100 URLs (if applicable) : Other browsers tested: No What steps will reproduce the problem? (1) install Node and Light House module on Redhat linux machine (2) write a NodeJS script to execute 6 different urls of Retail vedors like amazon.com, target.com, kohls.com for 3 times and take the median value (3) script should launch headless chrome for these 6 urls and capture the parameters like speed index, time to interactive, First Content Load etc (4) store these values in to Elastic Search DB using Http Node Module What is the expected result? - script should execute successfully. What happens instead? - i have this script configured using crontab to run daily once. it ran successfully for couple of days. however, it started failing now. script seems to be shutting down after executing few urls. co-incidence issue i was reported was that, Memory full with /tmp folder notification reported. all i can see in tmp folder is some "lighthouse.xxxxx" folders created. i think these for GPU related. not sure what is causing the script to halt before completing the execution. Please provide any additional information below. Attach a screenshot if possible.
,
Oct 24
This doesn't seem actionable without more logs about the failures.
,
Oct 24
,
Oct 24
i found that those PIDs dated back to 1 month and has consumed entire space(4GB). so, i have killed those processes for now. i will monitor till tomorrow to see if any open chrome PIDs exist after the script execution and will update here.
,
Oct 24
Thank you for providing more feedback. Adding the requester to the cc list. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
Oct 26
No instances of chrome found now. "pidof chrome". please close this ticket.
,
Oct 26
Thanks for confirming. |
|||||
►
Sign in to add a comment |
|||||
Comment 1 by rkoll...@nisum.com
, Oct 24