Nikolay Vitkov
Nikolay Vitkov
We have tracked down the issue to [HttpsUpgrades](https://chromestatus.com/feature/6056181032812544). I will file an issue upstream and update this comment with it. If you disable it, you should stop seeing this. ```ts...
I think this is the Firefox issue relate to this - https://bugzilla.mozilla.org/show_bug.cgi?id=1841125
Does the issue reproduce for you locally? If so could you either provide a fully reproducible example with variables included. Or if its only after deploying collect logs via setting...
@Satelliting Puppeteer use the the same PDF printing mechanism as Chrome, can you verify if you are experiencing this on normal headful Chrome when using `Print... (Ctrl+P)`? If so you...
I can reproduce the issue and found the root cause of it.
@RayburnTrading Do you see the same issue if you use the official [Puppeteer Docker image](https://github.com/puppeteer/puppeteer/pkgs/container/puppeteer)? I can see that we do set a separate `user` for it - [Dockerfile](https://github.com/puppeteer/puppeteer/blob/main/docker/Dockerfile).
Like you have observed this behavior comes from Chrome itself. From my understanding the issue is running out of memory or disk. Please verify that if that's the case. Also...
@AnicetJonhia Could you verify that the `.social-details-reactors-tab-body-list-item` exists if you to the previous steps in headful (`await puppeteer.launch({ headless: false });`). Sadly I am unable to reproduce due to not...
Note: I think this is related to CI performance and browser boot-up times, due to the volume of things we do. An option is to shard this to test runners...