Patrick Klingemann
Patrick Klingemann
@mfncooper we've verified this PR fixes the memory leak we were seeing. Any chance of getting this merged?
I'm running latest master, published to my org's npm repo. #187 I believe is a different issue.
@adieuadieu that's from node in the terminal, but the errors show in cloudwatch as well: ``` START RequestId: 31d738d2-8832-11e7-ae39-bf58b5654704 Version: $LATEST 2017-08-23T18:38:02.445Z 31d738d2-8832-11e7-ae39-bf58b5654704 @serverless-chrome/lambda Spawning headless shell 2017-08-23T18:38:02.446Z 31d738d2-8832-11e7-ae39-bf58b5654704 @serverless-chrome/lambda...
@adieuadieu do you have any thoughts on where to start looking to track this down? I've been troubleshooting for some time but typescript, async/await are both pretty new to me...
this could be a duplicate of: https://github.com/graphcool/chromeless/issues/153
I can confirm that @TravelingTechGuy's timeout solution from #153 improved things for me. Tried to find a more foolproof solution without any luck. It could have something to do with...
@adieuadieu I will give it a try and report back.
I've done a lot of research on this issue and I'm pretty certain it's related to https://github.com/adieuadieu/serverless-chrome/issues/41. @adieuadieu can you confirm?
see https://developers.google.com/web/updates/2017/04/headless-chrome#faq