-
-
Notifications
You must be signed in to change notification settings - Fork 28
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
"Unable to get new page, browser likely crashed" #400
Comments
The same with 50 workers. |
This may or may not be related to #376, since this doesn't crash node, but seems like browser may be crashing eventually. 100 or 50 works is quite a lot, unless you have an incredible powerful machine, the RAM/CPU requirements for running 50 browser windows in parallel is likely not going to be enough. I would try with 2 or 4 workers first. |
Running on old laptop: 16 GB of DDR3 RAM. For the last 2 days running with 20 workers - no errors. |
Glad that it's working! For a most static site, the memory usage is much lower. If you run into issues, would try with less workers. |
The text was updated successfully, but these errors were encountered: