New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We鈥檒l occasionally send you account related emails.
Already on GitHub? Sign in to your account
Puppeteer browser.close() hangs on AWS Lambda #95
Comments
|
Thanks @JacksonGL for the idea 馃挭 |
Hello @JacksonGL I assume you haven't looked into this problem? Thank you |
@doteric Feel free to create a PR, I am happy to review it |
@JacksonGL |
@doteric I left a comment on the PR. |
@doteric Please check and accept the CLA agreement so I can import and integrate your PR. https://github.com/facebook/memlab/blob/main/CONTRIBUTING.md#contributor-license-agreement-cla |
Hello 馃憢
I have been having a problem running MemLab in an AWS Lambda (NodeJS v18) timing out no matter what time it is given and decided to investigate what's wrong. After a bit of investigation trying with and wihtout the warmup it looked like MemLab does all the needed work, but just fails to finish off and end, looked into it further and it seems to be an exact same problem that I had somewhere else with puppeteer.
Sparticuz/chromium#85 (comment)
The issue was that the browser can not close properly for some reason, but when all the pages are closed beforehand then it closes all fine. However this is not the case in this situation and I am still experiencing the
browser.close()
hanging even with the following code of MemLab:Any other ideas what could be wrong?
To add to this I could not use the defined
pages
as the passed array is[page]
(insidetestInBrowser
) and does not include any other pages (not expected, but possible) therefore it is safer to just look for all the pages again withawait browser.pages()
Puppeteer chromium flags just FYI if they would matter by any chance (one part from MemLab, other part from
@sparticuz/chromium
.The text was updated successfully, but these errors were encountered: