Comments (4)
The page will be closed as soon as your task function is executed.
But you can use a Promise to wait until you are done. Then you call the resolve
function to close the page.
await cluster.task(async ({ data, page }) => {
await new Promise((resolve) => {
// do some asynchronous stuff
// maybe call an async function like setTimeout?
setTimeout(() => {
// do more stuff...
// When we are done we call resolve() to resolve the promise
resolve(); // this will finish the task function and the page will be closed
}, 3000);
});
});
Be careful with asynchronous functions though. Asynchronously thrown errors cannot be caught by the library. So don't forget try-catch blocks where necessary.
from puppeteer-cluster.
It is done automatically. As soon as your task function finishes (or a timeout happens) the opened resources will be closed. You do not need to worry about that.
If you want to see it in action, you can run puppeteer locally and disable headless mode.
from puppeteer-cluster.
Thanks for the response, @thomasdondorf. Another question came to my mind: is the page.close()
done by puppeteer-cluster
? Asking because had a lot of Protocol error (Page.navigate): Target closed., stack=Error: Protocol error (Page.navigate): Target closed.
during the ~45 mins of run of a process.
from puppeteer-cluster.
Another question: can I control page termination myself without relying on automation? It seems for now it getting closed (lost context) before all operations are completed.
from puppeteer-cluster.
Related Issues (20)
- Clear up Concurrency wording incorrect usage HOT 5
- Feature: Lifetimes
- How To Stop Worker To Become Idle automatically
- Expose stats via prometheus HOT 2
- Screen shot getting stuck forever
- Use same URL but diffetent logic on each browser HOT 1
- Concurrency launch: CONCURRENCY_BROWSER definition slightly misleading HOT 2
- Error detection super slow with new Puppeteer versions HOT 1
- Support to new puppetter versions HOT 1
- share the dockerfile I'm using
- Suggestion: Allow pool of already instantiated browser workers
- how to open the progress view and monitoring statistics? HOT 1
- cluster concurrent seems not work HOT 1
- Regarding resource usage HOT 1
- Worker Error getting browser page HOT 1
- How to set args like .launch({ args: [] }) ? HOT 3
- Has anyone managed to use separate data for each browser?
- browser crushing due to "open /sys/devices/system/cpu/cpu0/cpufreq/scaling_cur_freq: No such file or directory (2)"
- puppeteer-v22.0.0 breaking changes HOT 2
- concurrent limit?
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from puppeteer-cluster.