Headless Chrome slows tests by 10x #561

fatso83 · 2017-06-19T13:48:09Z

What are you trying to achieve?

I am trying to run my tests in headless Chrome using the --headless argument. I expect the tests to run in approximately the same amount of time as the usual runs, as running a clean webdriverio script runs faster headless than in a normal browser window.

What do you get instead?

The tests run about ten times as slow, using 44 seconds instead of 4 seconds.

$ time $(npm bin)/codeceptjs run --verbose > headless-output.txt

real	0m44.973s
user	0m0.992s
sys	0m0.068s

$ nvim codecept.json # removing --headless option

developer at developer-XPS-13-9360 in ~/dev/dx-nuflo/tests/acceptance (acceptance-testing)
$ time $(npm bin)/codeceptjs run --verbose > output.txt

real	0m4.879s
user	0m0.768s
sys	0m0.088s

verbose output from headless run

CodeceptJS v0.6.3
Using test root "/home/developer/dev/dx-nuflo/tests/acceptance"

Top level-routes --
   [1] Starting recording promises
   Emitted | suite.before ([object Object])
   [1] Queued | hook WebDriverIO._beforeSuite()
 a page to add a new encounter should be rendered
 > [Session] Starting singleton browser session
   [2] Starting recording promises
   Emitted | test.before
   [2] Queued | hook WebDriverIO._before()
   Emitted | test.start ([object Object])
   Emitted | step.before (I am on page "/encounter/new")
   [2] Queued | amOnPage: "/encounter/new"
   Emitted | step.after (I am on page "/encounter/new")
   [2] Queued | return step result
   Emitted | step.before (I see "LOGG INN")
   [2] Queued | see: "LOGG INN"
   Emitted | step.after (I see "LOGG INN")
   [2] Queued | return step result
   [2] Queued | fire test.passed
   [2] Queued | finish test
   Emitted | step.start (I am on page "/encounter/new")
 • I am on page "/encounter/new"
   Emitted | step.start (I see "LOGG INN")
 • I see "LOGG INN"
   Emitted | test.passed ([object Object])
 ✓ OK in 22317ms

   Emitted | test.after
   [2] Queued | hook WebDriverIO._after()
 > [Session] cleaning cookies and localStorage
 fooScen
   [3] Starting recording promises
   Emitted | test.before
   [3] Queued | hook WebDriverIO._before()
   Emitted | test.start ([object Object])
   Emitted | step.before (I am on page "/encounter/new")
   [3] Queued | amOnPage: "/encounter/new"
   Emitted | step.after (I am on page "/encounter/new")
   [3] Queued | return step result
   Emitted | step.before (I see "FOOLOGG INN")
   [3] Queued | see: "FOOLOGG INN"
   Emitted | step.after (I see "FOOLOGG INN")
   [3] Queued | return step result
   [3] Queued | fire test.passed
   [3] Queued | finish test
   Emitted | step.start (I am on page "/encounter/new")
 • I am on page "/encounter/new"
   Emitted | step.start (I see "FOOLOGG INN")
 • I see "FOOLOGG INN"
   [3] Error | Error
   [3] Starting <teardown> session
   Emitted | test.failed ([object Object])
   [3] <teardown> Queued | hook WebDriverIO._failed()
   [3] <teardown> Queued | () => done(err)
   [3] <teardown> Stopping recording promises
 > Screenshot has been saved to /home/developer/dev/dx-nuflo/tests/acceptance/output/fooScen.failed.png
 ✖ FAILED in 11599ms

   Emitted | test.after
   [3] <teardown> Queued | hook WebDriverIO._after()
 > [Session] cleaning cookies and localStorage
   [4] Starting recording promises
   Emitted | suite.after ([object Object])
   [4] Queued | hook WebDriverIO._afterSuite()

-- FAILURES:

  1) Top level-routes: fooScen:

      expected web page to include "FOOLOGG INN"
      + expected - actual

      -Innlogging
      -Brukernavn
      -Passord
      -LOGG INN
      +FOOLOGG INN
      
  
  Scenario Steps:
  
  - I.see("FOOLOGG INN") at Test.Scenario (top-level-routes_test.js:18:5)
  - I.amOnPage("/encounter/new") at Test.Scenario (top-level-routes_test.js:14:5)
  
  Error
      at Object.<anonymous> (/home/developer/dev/dx-nuflo/node_modules/codeceptjs/lib/helper/WebDriverIO.js:1129:51)
      at Object.exec (/home/developer/dev/dx-nuflo/node_modules/webdriverio/build/lib/helpers/safeExecute.js:28:24)
      at Object.resolve (/home/developer/dev/dx-nuflo/node_modules/webdriverio/build/lib/webdriverio.js:189:29)
      at /home/developer/dev/dx-nuflo/node_modules/webdriverio/build/lib/webdriverio.js:538:32
      at _fulfilled (/home/developer/dev/dx-nuflo/node_modules/q/q.js:854:54)
      at self.promiseDispatch.done (/home/developer/dev/dx-nuflo/node_modules/q/q.js:883:30)


  FAIL  | 1 passed, 1 failed   // 34s
   Emitted | global.result ([object Object])


real	0m44.973s
user	0m0.992s
sys	0m0.068s

verbose output from normal (non-headless) run

CodeceptJS v0.6.3
Using test root "/home/developer/dev/dx-nuflo/tests/acceptance"

Top level-routes --
   [1] Starting recording promises
   Emitted | suite.before ([object Object])
   [1] Queued | hook WebDriverIO._beforeSuite()
 a page to add a new encounter should be rendered
 > [Session] Starting singleton browser session
   [2] Starting recording promises
   Emitted | test.before
   [2] Queued | hook WebDriverIO._before()
   Emitted | test.start ([object Object])
   Emitted | step.before (I am on page "/encounter/new")
   [2] Queued | amOnPage: "/encounter/new"
   Emitted | step.after (I am on page "/encounter/new")
   [2] Queued | return step result
   Emitted | step.before (I see "LOGG INN")
   [2] Queued | see: "LOGG INN"
   Emitted | step.after (I see "LOGG INN")
   [2] Queued | return step result
   [2] Queued | fire test.passed
   [2] Queued | finish test
   Emitted | step.start (I am on page "/encounter/new")
 • I am on page "/encounter/new"
   Emitted | step.start (I see "LOGG INN")
 • I see "LOGG INN"
   Emitted | test.passed ([object Object])
 ✓ OK in 2748ms

   Emitted | test.after
   [2] Queued | hook WebDriverIO._after()
 > [Session] cleaning cookies and localStorage
 fooScen
   [3] Starting recording promises
   Emitted | test.before
   [3] Queued | hook WebDriverIO._before()
   Emitted | test.start ([object Object])
   Emitted | step.before (I am on page "/encounter/new")
   [3] Queued | amOnPage: "/encounter/new"
   Emitted | step.after (I am on page "/encounter/new")
   [3] Queued | return step result
   Emitted | step.before (I see "FOOLOGG INN")
   [3] Queued | see: "FOOLOGG INN"
   Emitted | step.after (I see "FOOLOGG INN")
   [3] Queued | return step result
   [3] Queued | fire test.passed
   [3] Queued | finish test
   Emitted | step.start (I am on page "/encounter/new")
 • I am on page "/encounter/new"
   Emitted | step.start (I see "FOOLOGG INN")
 • I see "FOOLOGG INN"
   [3] Error | Error
   [3] Starting <teardown> session
   Emitted | test.failed ([object Object])
   [3] <teardown> Queued | hook WebDriverIO._failed()
   [3] <teardown> Queued | () => done(err)
   [3] <teardown> Stopping recording promises
 > Screenshot has been saved to /home/developer/dev/dx-nuflo/tests/acceptance/output/fooScen.failed.png
 ✖ FAILED in 1299ms

   Emitted | test.after
   [3] <teardown> Queued | hook WebDriverIO._after()
 > [Session] cleaning cookies and localStorage
   [4] Starting recording promises
   Emitted | suite.after ([object Object])
   [4] Queued | hook WebDriverIO._afterSuite()

-- FAILURES:

  1) Top level-routes: fooScen:

      expected web page to include "FOOLOGG INN"
      + expected - actual

      -Innlogging
      -Brukernavn
      -Passord
      -LOGG INN
      +FOOLOGG INN
      
  
  Scenario Steps:
  
  - I.see("FOOLOGG INN") at Test.Scenario (top-level-routes_test.js:18:5)
  - I.amOnPage("/encounter/new") at Test.Scenario (top-level-routes_test.js:14:5)
  
  Error
      at Object.<anonymous> (/home/developer/dev/dx-nuflo/node_modules/codeceptjs/lib/helper/WebDriverIO.js:1129:51)
      at Object.exec (/home/developer/dev/dx-nuflo/node_modules/webdriverio/build/lib/helpers/safeExecute.js:28:24)
      at Object.resolve (/home/developer/dev/dx-nuflo/node_modules/webdriverio/build/lib/webdriverio.js:189:29)
      at /home/developer/dev/dx-nuflo/node_modules/webdriverio/build/lib/webdriverio.js:538:32
      at _fulfilled (/home/developer/dev/dx-nuflo/node_modules/q/q.js:854:54)
      at self.promiseDispatch.done (/home/developer/dev/dx-nuflo/node_modules/q/q.js:883:30)


  FAIL  | 1 passed, 1 failed   // 4s
   Emitted | global.result ([object Object])


real	0m4.879s
user	0m0.768s
sys	0m0.088s

Test source code

Feature('Top level-routes');

Scenario('a page to add a new encounter should be rendered', (I) => {
  I.amOnPage('/encounter/new');
  I.see('LOGG INN');
});

// just to see how a failing test looks
Scenario('fooScen', (I) => {
  I.amOnPage('/encounter/new');
  I.see('FOOLOGG INN');
});

Details

CodeceptJS version: 0.6.3
NodeJS Version: 8.1.2
Operating System: Ubuntu 16.04 LTS
WebDriverIO: 4.8.0
Configuration file:

This is my configuration:

{
  "tests": "./*_test.js",
  "timeout": 5000,
  "output": "./output",
  "helpers": {
    "WebDriverIO" : {
      "browser": "chrome",
      "desiredCapabilities": {
          "browserName": "chrome",
          "chromeOptions": {
              "args": [
                  "headless",
                  "disable-gpu"
              ]
          }
      },
      "windowSize": "320x568",
      "restart": false,
      "timeouts": {
        "script": 10000,
        "page load": 3000,
        "implicit" : 5000
      },
      "url": "http://localhost:23450"
    }
  },
  "include": {
    "I": "./steps_file.js"
  },
  "bootstrap": false,
  "mocha": {},
  "name": "acceptance tests",
  "windowSize": "320x568"
}

The text was updated successfully, but these errors were encountered:

laurentpayot · 2017-06-27T16:29:58Z

@fatso83 Did you try with node < 8 such as 7.10.0?

fatso83 · 2017-06-27T17:52:33Z

Tried with Node 7.4.0. Still a lot slower.

A test run took 26 seconds with the non-headless browser and 1m5s with --headless. Not 10x slow, but at least 4x slower (probably due to more page loading in these tests, obscuring performance).

DavertMik · 2017-07-05T23:10:35Z

Thanks, I will investigate this issue

DavertMik · 2017-07-06T00:18:44Z

I reproduced the issue but I still have no clue what's wrong.
Just changing Chrome from headless to window makes test run much faster. Can this be caused because by disable-gpu flag? I don't know. Probably headless Chrome is not so stable enough

Setitch · 2017-10-11T09:52:46Z

I see the same slowness with and without --dissable-gpu so thats not the case. When i connect to the headless i see SO MANY ssl warning and so on - i think its just due to that.

DavertMik · 2017-10-11T11:41:12Z

Thanks. Maybe this could be the case

mogryo · 2017-12-07T07:01:49Z

Hey. Is there any updates on this issue? We've ran into similar problem on some of our machines. Our tests just timeout because of the enormous time it takes for headless chrome to do what we ask. And if launched not in headless it runs smooth.

We ran into this problem on windows 7. With latest chromedriver 2.33 and latest chrome. But it's very random. On other machines with the same configuration it runs perfectly in headless (well, not exactly perfectly, but only ~1.5x times slower). Perhaps you have an idea what should we check on these machines? to pin point the mystical difference between them.

emesterhazy · 2018-02-04T20:51:54Z

Also experiencing extremely slow load times when using Chrome in headless mode in Windows 7 with the latest version of Chromedriver, Chrome, and Selenium. Interestingly I'm not having any issues on Windows 10.

JamesLMilner · 2018-02-16T14:51:59Z

I'm coming at this from a different place, but interestingly there's an open issue on ChromeDriver which sounds suspiciously related: https://bugs.chromium.org/p/chromedriver/issues/detail?id=2054&q=jenkins&colspec=ID%20Status%20Pri%20Owner%20Summary

laskeym · 2018-02-23T19:56:07Z

I'm in the same boat as @emesterhazy . I currently have Chrome Version 63.0.3239.132 and ChromeDriver 2.35 on Windows 7 and headless hangs up on retrieving the sites. When I come home from work, I'll mess around with this on my Debian 9 and Windows 10 machine and report the results.

Simple test of retrieving the Facebook home page and grabbing login forms:
Windows 7:

Headless = 111.667s
Non-Headless = 3.018s

Also, I have Google Chrome Canary downloaded, but I haven't attempted to configure the driver to use it. Not sure if using Canary over standard Chrome would make a difference.

oligee80 · 2018-03-16T10:12:45Z

Try these two ChromeOptions:

options.addArguments("--proxy-server='direct://'");
options.addArguments("--proxy-bypass-list=*");

I dunno in wich forum it was but this did the trick for me

hYpac0w · 2018-03-22T13:36:57Z

@oligee80 THANK YOU SO MUCH!
These options finally got headless chrome working for me :)

Resh5 · 2018-04-09T16:38:10Z

@oligee80 Thanks much!!! It worked for me as well.

yashwanth2804 · 2018-04-17T10:11:01Z

@oligee80 Really thank you buddy, I have been breaking my head for that issue, finally got worked out

rahul-konduru · 2018-04-25T07:26:31Z

I am trying this on win 10. After adding the arguments that @oligee80 has mentioned, I do not see any difference. Is there something else that I should be doing?

Resh5 · 2018-04-25T16:30:18Z

@krrahulmanikanta Is your Chrome version compatible?

rahul-konduru · 2018-04-25T17:27:16Z

@Resh5 Yes, I am using chromedriver v2.38 and my chrome is of v66

Resh5 · 2018-04-25T17:48:22Z

@krrahulmanikanta It workes fine for me . But I am in Windows7
System.setProperty("path to driver);
ChromeOptions chromeOptions = new ChromeOptions();
chromeOptions.addArguments("--headless");
chromeOptions.addArguments("window-sized1200,600");
chromeOptions.addArguments("--proxy-server='direct://'");
chromeOptions.addArguments("--proxy-bypass-list=*");
ChromeDriver driver = new ChromeDriver(chromeOptions);

Robula · 2018-05-17T17:03:20Z

I'm seeing a similar issue using Puppeteer and Chromium (no WebDriver), the proxy arguments do not seem to make a difference in my case. This may be an issue related to Chromium.

macOS: 10.13.4
Node: 8.10.0
headless: true results in 7747.209ms
headless: false results in 4775.771ms

And decrease single test timeout, optimistically. See codeceptjs/CodeceptJS#561 (comment)

oppahansi · 2018-12-26T01:38:44Z

@oligee80 Thanks

pardovot · 2019-05-18T13:54:11Z

Try these two ChromeOptions:
options.addArguments("--proxy-server='direct://'");
options.addArguments("--proxy-bypass-list=*");
I dunno in wich forum it was but this did the trick for me

Don't know if you'll actually see this, but it seems like the following solved the issue for me: options.addArguments("--proxy-server=");
The question is, why? I'm running the simplest code ever which is something like:
new WebDriver, driver.get("https://www.google.com").
This takes around 2 minutes, and solved be that argument, but I really can't understand what exactly it does..
Thanks! :)

GeorgeDubuque · 2019-07-21T00:15:38Z

I am having a similar issue on this one still. I tried with the following arguments

options.add_argument("--proxy-server='direct://'")
options.add_argument("--proxy-bypass-list=*")
options.add_argument("--proxy-server=")

I am still not seeing any speed up. 40 seconds to run in headless and 4 seconds to run in windowed mode. I am running ChromeDriver 75.0.3770.140.

Please let me know if anyone solves this one! Could really help me out. All I am doing is calling driver.get("https://www.google.com")

GeorgeDubuque · 2019-07-21T00:38:57Z

I am having a similar issue on this one still. I tried with the following arguments
options.add_argument("--proxy-server='direct://'")
options.add_argument("--proxy-bypass-list=*")
options.add_argument("--proxy-server=")
I am still not seeing any speed up. 40 seconds to run in headless and 4 seconds to run in windowed mode. I am running ChromeDriver 75.0.3770.140.

Please let me know if anyone solves this one! Could really help me out. All I am doing is calling driver.get("https://www.google.com")

Ok so after looking into it a bit more it seems that avoiding using headless chrome is the solution for me. Instead I use the pyvirtualdisplay library and set its visibilty to false. This sped up my performance 10x. Here is the code:

from selenium import webdriver
from pyvirtualdisplay import Display
import time

start = time.time()
display = Display(visible=0, size=(800, 600))
display.start()
driver = webdriver.Chrome(
        "/home/george/Desktop/chromedriver")
driver.get("https://www.google.com")
driver.quit()
display.stop()
end = time.time()
print(end-start)

with output:

5.253071069717407

instead of:

42.1179986000061

HansHagberg · 2019-08-14T10:59:42Z

Was searching for solution to a similar problem so I'm adding a note for reference:

Running a test scenario with headless Chromium and 100 instances. Machine is an AMD 2950X with 16 phys cores @4 GHz, 128 GB RAM and an Nvidia GTX 1660 GPU on Windows 10. This machine turns into a sluggish mess when running this with GPU-disabled in chromium startup. With GPU enabled, response is acceptable. With 200 clients, machine goes very sluggish (useless) again even with GPU.

With 200 instances, GPU utilization is very low (<10%) and CPU is ~35%
Task manager says 17300 threads and 420000 handles.

It seems to be some windows resource causing degradation because when doing a remote login session with another account while the load is running, the new session has no problems with response. So it looks like Windows and not the hardware is the bottleneck. Contemplating trying with Windows server to see if that helps.

Update: Windows server 2019 made no difference

Running headless instances in tabs instead seems to stress the system a lot less. We can now run 4 - 5 times as many instances with less problems compared to 200 instances before.

wilsonweb · 2019-11-06T13:35:57Z

I saw some people get this to work and others do not have any success with it:

chromeOptions.addArguments("--proxy-server='direct://'");
chromeOptions.addArguments("--proxy-bypass-list=*");

I did not have success at first ether, then I looked at my code and realized that I have called setChromeOptions() more than one time and wondered if options are getting over-written. I moved things around to make only one call to setChromeOptions() and it worked.

var $driver = require("selenium-webdriver");
let chrome = require("selenium-webdriver/chrome");

const chromeOptions = new chrome.Options();//.headless();
chromeOptions.addArguments("--headless"); 
chromeOptions.addArguments("--proxy-server='direct://'");
chromeOptions.addArguments("--proxy-bypass-list=*");
chromeOptions.addArguments("window-size=1024,1324");
chromeOptions.addArguments("--blink-settings=imagesEnabled=false"); 

var $browser = new $driver.Builder()
	.forBrowser("chrome")
	.setChromeOptions(chromeOptions) 
	.withCapabilities(capabilities)
	//.forBrowser('firefox')
	.build();

You can ignore the lines dealing with hiding images, windows size etc. if you choose.

zjhgx · 2020-11-24T14:09:02Z

in my case, add the following argument solve my problem
chrome_options.add_argument('blink-settings=imagesEnabled=false')

mikemangas · 2022-01-24T10:12:32Z

options.addArguments("--proxy-server='direct://'");
options.addArguments("--proxy-bypass-list=*");

Where do you insert this?

@oligee80

Find this fix at codeceptjs/CodeceptJS#561

mys1erious · 2023-02-13T14:07:14Z

Only thing that worked for me is adding UserAgent to the options:
options.add_argument("user-agent=Chrome/110.0.5481.77")

fatso83 changed the title ~~Passing headless option to Chrome wdio slows tests by 10x~~ Headless Chrome slows tests by 10x Jun 19, 2017

APshenkin added the need investigation label Jul 27, 2017

HughZurname mentioned this issue Aug 4, 2017

[Enhancement] - Chromeless Helper #649

Closed

JamesLMilner mentioned this issue Feb 16, 2018

Figure out why headless Chrome/Firefox are so slow with Unity 2017.3 3drepo/3drepo.io#743

Closed

shaunOclcl mentioned this issue Apr 3, 2018

Ubuntu: Cannot start ChromeHeadless karma-runner/karma-chrome-launcher#175

Open

ChiggerChug mentioned this issue Jun 15, 2018

Puppeteer with headless:true is extremely slow puppeteer/puppeteer#1718

Closed

softwareklinic mentioned this issue Jun 28, 2018

Using --block options sitespeedio/sitespeed.io#2074

Closed

segl84 mentioned this issue Jul 19, 2018

Testem Chrome Timeouts testem/testem#1021

Closed

analogrelay mentioned this issue Aug 29, 2018

fix chrome headless lag on Win7 aspnet/SignalR#2890

Merged

timorantalaiho added a commit to Opetushallitus/omatsivut that referenced this issue Sep 17, 2018

Improve headless Chrome performance

4648464

And decrease single test timeout, optimistically. See codeceptjs/CodeceptJS#561 (comment)

timorantalaiho added a commit to Opetushallitus/omatsivut that referenced this issue Sep 18, 2018

Improve headless Chrome performance

30ed3ad

And decrease single test timeout, optimistically. See codeceptjs/CodeceptJS#561 (comment)

GlassGruber mentioned this issue Jan 19, 2019

Slow/weird network requests electron/electron#13829

Closed

vbanos mentioned this issue May 14, 2019

Add headless chrome option internetarchive/brozzler#152

Closed

laneschmidt mentioned this issue Oct 2, 2019

Cannot start ChromeHeadless in Angular project, WSL karma-runner/karma-chrome-launcher#214

Open

mt025 mentioned this issue Jan 19, 2021

Timeout Error NiciusB/twitch-drops-lurker#9

Open

DavertMik closed this as completed Sep 5, 2021

fish3046 mentioned this issue Jan 14, 2022

[1.3] Add support for --no-proxy-server and --proxy-bypass-list Chrome args chrome-php/chrome#312

Merged

il12 added a commit to il12/livekit-recorder that referenced this issue May 20, 2022

Add possible fix to chrome stucked

8ff8bd9

Find this fix at codeceptjs/CodeceptJS#561

il12 mentioned this issue May 20, 2022

Add possible fix to chrome stucked il12/livekit-recorder#1

Merged

mikelehen mentioned this issue Jan 31, 2023

Increase function memory and speed up chromium act-now-coalition/act-now-links-service#41

Merged

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Headless Chrome slows tests by 10x #561

Headless Chrome slows tests by 10x #561

fatso83 commented Jun 19, 2017 •

edited

Loading

laurentpayot commented Jun 27, 2017

fatso83 commented Jun 27, 2017

DavertMik commented Jul 5, 2017

DavertMik commented Jul 6, 2017

Setitch commented Oct 11, 2017

DavertMik commented Oct 11, 2017

mogryo commented Dec 7, 2017 •

edited

Loading

emesterhazy commented Feb 4, 2018

JamesLMilner commented Feb 16, 2018

laskeym commented Feb 23, 2018 •

edited

Loading

oligee80 commented Mar 16, 2018

hYpac0w commented Mar 22, 2018

Resh5 commented Apr 9, 2018

yashwanth2804 commented Apr 17, 2018 •

edited

Loading

rahul-konduru commented Apr 25, 2018

Resh5 commented Apr 25, 2018

rahul-konduru commented Apr 25, 2018

Resh5 commented Apr 25, 2018

Robula commented May 17, 2018

oppahansi commented Dec 26, 2018

pardovot commented May 18, 2019

GeorgeDubuque commented Jul 21, 2019

GeorgeDubuque commented Jul 21, 2019

HansHagberg commented Aug 14, 2019 •

edited

Loading

wilsonweb commented Nov 6, 2019

zjhgx commented Nov 24, 2020

mikemangas commented Jan 24, 2022 •

edited

Loading

mys1erious commented Feb 13, 2023

Headless Chrome slows tests by 10x #561

Headless Chrome slows tests by 10x #561

Comments

fatso83 commented Jun 19, 2017 • edited Loading

What are you trying to achieve?

What do you get instead?

Test source code

Details

laurentpayot commented Jun 27, 2017

fatso83 commented Jun 27, 2017

DavertMik commented Jul 5, 2017

DavertMik commented Jul 6, 2017

Setitch commented Oct 11, 2017

DavertMik commented Oct 11, 2017

mogryo commented Dec 7, 2017 • edited Loading

emesterhazy commented Feb 4, 2018

JamesLMilner commented Feb 16, 2018

laskeym commented Feb 23, 2018 • edited Loading

oligee80 commented Mar 16, 2018

hYpac0w commented Mar 22, 2018

Resh5 commented Apr 9, 2018

yashwanth2804 commented Apr 17, 2018 • edited Loading

rahul-konduru commented Apr 25, 2018

Resh5 commented Apr 25, 2018

rahul-konduru commented Apr 25, 2018

Resh5 commented Apr 25, 2018

Robula commented May 17, 2018

oppahansi commented Dec 26, 2018

pardovot commented May 18, 2019

GeorgeDubuque commented Jul 21, 2019

GeorgeDubuque commented Jul 21, 2019

HansHagberg commented Aug 14, 2019 • edited Loading

wilsonweb commented Nov 6, 2019

zjhgx commented Nov 24, 2020

mikemangas commented Jan 24, 2022 • edited Loading

mys1erious commented Feb 13, 2023

fatso83 commented Jun 19, 2017 •

edited

Loading

mogryo commented Dec 7, 2017 •

edited

Loading

laskeym commented Feb 23, 2018 •

edited

Loading

yashwanth2804 commented Apr 17, 2018 •

edited

Loading

HansHagberg commented Aug 14, 2019 •

edited

Loading

mikemangas commented Jan 24, 2022 •

edited

Loading