You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Which package is this bug report for? If unsure which one to select, leave blank
@crawlee/core
Issue description
Hey there,
We have an actor on the Apify Store (https://apify.com/epctex/traffic-generator) that produces an Error: Page closed error randomly without properly catching it and causing the actor to crash. The problem is not easily producible but in the local machines, you can reproduce it by running the actor and force abort it by hitting multiple cmd + C.
We do not wait for any responses or promises. We only use preNavigationHooks for blocking the requests by using crawlee utils. For detailed code inspection, we can have a call or you can reach out to me via Slack.
Note: This is not the same issue with this one since the error got produced directly from the playwright library rather than Crawlee or Apify SDK.
Code sample
No response
Package version
3.9.2
Node.js version
18
Operating system
apify/actor-node-playwright-chrome:18
Apify platform
Tick me if you encountered this issue on the Apify platform
I have tested this on the next release
No response
Other context
No response
The text was updated successfully, but these errors were encountered:
Which package is this bug report for? If unsure which one to select, leave blank
@crawlee/core
Issue description
Hey there,
We have an actor on the Apify Store (https://apify.com/epctex/traffic-generator) that produces an
Error: Page closed
error randomly without properly catching it and causing the actor to crash. The problem is not easily producible but in the local machines, you can reproduce it by running the actor and force abort it by hitting multiple cmd + C.The screenshot is attached and this is the Run.
We do not wait for any responses or promises. We only use
preNavigationHooks
for blocking the requests by using crawlee utils. For detailed code inspection, we can have a call or you can reach out to me via Slack.Note: This is not the same issue with this one since the error got produced directly from the playwright library rather than Crawlee or Apify SDK.
Code sample
No response
Package version
3.9.2
Node.js version
18
Operating system
apify/actor-node-playwright-chrome:18
Apify platform
I have tested this on the
next
releaseNo response
Other context
No response
The text was updated successfully, but these errors were encountered: