-
Notifications
You must be signed in to change notification settings - Fork 168
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’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Iframe with bad src causing timeouts since version 1.4.0 #257
Comments
Hi, this should be a problem specifically for your website - can you confirm that it works for a completely different url? Can you please share a publicly accessible url that you have this problem with that I can debug? If you have this problem for any website you test, then it's something about your environment. If so please share your OS, node version, anything else you think is relevant. Cheers |
Hi again! Well it seems to be a resource problem. I am generating critical CSS for a lot of urls (>25) without any queue system. I will try to implement this and return. |
So i was too quick but i managed to fix the error. The error appears when i have an iframe in the following format: <iframe style="width:100%" width="560" height="400" id="youtube"
src="?rel=0&controls=1&showinfo=0"
frameborder="0" allow="autoplay; encrypted-media" allowfullscreen></iframe> But changning the src to a valid URL everything works as expected. <iframe style="width:100%" width="560" height="400" id="youtube"
src="https://google.com?rel=0&controls=1&showinfo=0"
frameborder="0" allow="autoplay; encrypted-media" allowfullscreen></iframe> Btw. i am using Node v9.7.0. |
Interesting, I will try to reproduce. |
I can reproduce, any page with that iframe never loads. Indeed this worked before, it broke when Penthouse upgraded to Puppeteer@1.0.0. I'm guessing your iframe src is not found and how Puppeteer now works it never resolves the Page.load promise. Puppeteer has changed a bit since the 1.0.0 version, but Penthouse has been blocked from upgrading. In the next release however an upgrade should be possible, so I'll come back to revisit this then to see if this issue can be resolved. |
Looks like this was indeed resolved with the latest Puppeteer version, now available in latest penthouse (1.4.5), via #261 |
If you test and somehow this fix does not work for you, please re-open the issue. |
Hi!
I am getting the following error since version 1.4. It isn't a problem in version 1.3.0.
My config looks like this:
The text was updated successfully, but these errors were encountered: