So regarding headless: true that's because it's running on a Linux without GUI, defaultViewport: null is related to the width and height, it's not mandatory --incognito was for my use(in order to start without any cookies and etc.
and regarding the last three args
"--no-sandbox",
"--single-process",
"--no-zygote"
I'm not really sure, but that worked for me after a couple of tries...
Not sure what is running in Heroku that made this configuration worked for me:)
any reason why you came up with those launch options? Can't find documentation about those.
So regarding
headless: truethat's because it's running on a Linux without GUI,defaultViewport: nullis related to the width and height, it's not mandatory--incognitowas for my use(in order to start without any cookies and etc.and regarding the last three args
I'm not really sure, but that worked for me after a couple of tries...
Not sure what is running in Heroku that made this configuration worked for me:)
--no-sandboxi believe it means all page related process in main thread.peter.sh/experiments/chromium-comm...
--single-processmeans no parallelism for plugins and graphics.peter.sh/experiments/chromium-comm...
--no-zygoteno "main forker".peter.sh/experiments/chromium-comm...
That all together enforces only one chromium process.