-
-
Notifications
You must be signed in to change notification settings - Fork 564
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
JavaScript heap out of memory Alpine Linux #1268
Comments
Found that this occurs even with a much smaller number of files, particularly if a large set of them happen to change all at once (e.g. ~180 or so in my case, all of them You can test this by checking memory usage live as it's running. I do this by running the script in debug mode via: NODE_OPTIONS='--inspect' node test.js Then open Chrome DevTools, click the Node.js logo that comes up and then open the "Memory" tab. There you'll see this below. For me, it always starts out at 5MB. However, with the nested subdirectory glob pattern Edit: #1271 does a fantastic breakdown and I think that's actually what is happening here. |
The * wildcard had the same effect for us. We had to get rid of all globs/wildcards for not having the effect that the application allocates too much memory. Already 800 files at the same time exceeded the 1500MB max memory. |
Describe the bug
JavaScript heap out of memory
Versions:
To Reproduce:
I create 250000 files in FILE_DIR and get the memory leak, this code just log the messages
And the memory growth over time when create more files
The text was updated successfully, but these errors were encountered: