Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Memory/CPU runaway #138

Open
strarsis opened this issue Mar 27, 2021 · 1 comment
Open

Memory/CPU runaway #138

strarsis opened this issue Mar 27, 2021 · 1 comment

Comments

@strarsis
Copy link

When using this plugin for a larger number of sizes the CPU and memory go to 100% and my WSL 2 system basically crashes.
Is there a way to limit CPU/memory consumption?
@strarsis strarsis changed the title Memory/CPU overload Memory/CPU runaway Mar 27, 2021
@tsmith512
Copy link

tsmith512 commented Feb 27, 2022 •
edited

I have also run into this with WSL2 trying to make a pretty photo-heavy blog with Next.js. Memory usage can hit 14GB before it falls over. Haven't figured out what to do about it yet.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@tsmith512 @strarsis