Open Kwieeciol opened 1 month ago
Are you using JMalloc
?
When I upgraded from heroku-buildpack-google-chrome to this buildpack, puppeteer
stopped working no matter which shims I used.
I copied the four flags used by the previous buildpack
--headless --no-sandbox --disable-gpu --remote-debugging-port=9222
but I still got errors where Chrome was quitting on launch.
The only thing that fixed was to disable JMalloc
for node, by setting this env variable for Node as described here (we use Grover
)
I'm not sure why the other Chrome buildpack does not have this issue.
I'm not using JMalloc
Good morning, as I upgraded my stack on heroku I've noticed a message telling me to use this buildpack rather than the older buildpacks I've used. Logically I proceeded to install this buildpack per the instructions.
selenium.webdriver
works fine, butpyppeteer
doesn't work at all, this is the error I've encountered:I've tried all solutions available on StackOverflow, like installing the
puppeteer
buildpack, that doesn't work though, I've added the--disable-setuid-sandbox
argument to pyppeteer, doesn't work either.MRE: