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
[Bug]: Freezing when querying frames on certain websites #12292
Comments
This issue was not reproducible. Please check that your example runs locally and the following:
Once the above checks are satisfied, please edit your issue with the changes and we will |
I guess it cannot be reproduced by the workflow because it gets stuck? |
The promise frame.$$eval is never resolved. |
I think it is another example of #10696 basically the browser built-in PDF viewer creates empty iframes which never gets an execution context created for them as regular iframe. So the eval calls wait for the context as expected from the Chrome DevTools Protocol, but never gets them for those frames. Maybe it is because it is treated as part of the browser UI although the technical implementation is an iframe. |
A workaround could be like
or more general since it is reasonable to not expect any context on about:blank pages
|
Hi @OrKoN, We thought it might be a PDF issue in fact we tried filtering by PDF extension as you proposed in the first workaround. Although we didn't traverse the parent frames so this is why probably our solution didn't work. We will try your first workaround The second workaround is problematic. In fact in our solution we want to read frames with "about:blank". From our tests it results that calling |
You can also disable PDF viewer via OOPIFs for now via
|
Thank you, |
There is an issue for that https://issues.chromium.org/issues/40268279 |
I left a comment there as it looked like the feature was not meant to be enabled yet ? |
After further investigation, it looks like the feature might not be the reason for hanging (it seems to reproduce now with the feature disabled). It appears that the iframes from the pdf viewer extensions get reported into the page sessions via CDP (although they probably have to be contained to the extension target). |
I am experiencing freezing problem for |
Minimal, reproducible example
Error string
no error
Bug behavior
Background
We want to retrieve the links from the iframes within a website. This works for the majority of visited websites, but we noticed on certain websites this operation completely is freezing (the Promise is pending forever).
Running the reproducible example on http://fonologomed.it/ will freeze
For a contrarian example, running the reproducible example on https://www.aranzulla.it will NOT freeze
Expectation
The promise to resolve or at least get an error
Reality
The operation gets stuck as the Promise never gets resolved
Puppeteer configuration file (if used)
No response
Puppeteer version
22.6.5
Node version
20.3.0
Package manager
npm
Package manager version
9.6.7
Operating system
macOS
The text was updated successfully, but these errors were encountered: