-
Notifications
You must be signed in to change notification settings - Fork 42
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
Getting NULL on $page->content() #17
Comments
When i try directly with puppeteer, it's working : import puppeteer from "puppeteer";
const browser = await puppeteer.launch({});
const page = await browser.newPage();
await page.goto("https://www.nytimes.com/international/");
console.log(await page.content());
await browser.close(); |
I am facing the same null issue if data is too large I am getting a JSON from a page.
|
OK, thank you for your message. I think it's not Puphpeteer or Rialto bug but more a terminal buffer size wich change after an update. I face the same problem you describe developping a direct wrapper for a puppeteer script... my workaround was to store the terminal output in a file. So it should be quicker to find, change and test the OS buffer param for terminal. |
Try some stuff but without success, still getting null. |
I also Increase memory_limit on php.ini and Node limit but still same |
I'm facing the same issue. |
Describe the bug
Getting NULL on $page->content() randomly : on a few websites, it's working, on others not.
Reproducible example
I try with a blank new installation
When i set headless false, i can see the page is correctly loaded.
Generated logs
When i try to log it, i get :
Environment (please complete the following information):
My Node package manager is:
The text was updated successfully, but these errors were encountered: