-
Notifications
You must be signed in to change notification settings - Fork 30.1k
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
Out of memory errors as of v20y #47719
Labels
Comments
@nodejs/whatwg-stream |
We would need a reproduction to track this down. |
Has this been fixed in 20.1.0? |
As of 20.10, the memory is stable. This issue is probably fixed as well. |
we have a typescript project and running eslint on the project gives out of memory error in 20.10 where as in 20.9 it works fine. |
The issue is the same for 20.17 version in Bitrise step.
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Version
v20.0.0
Platform
Linux pathos 6.2.12-zen1-1-zen #1 ZEN SMP PREEMPT_DYNAMIC Thu, 20 Apr 2023 16:11:27 +0000 x86_64 GNU/Linux
Subsystem
memory (stream/web?)
What steps will reproduce the bug?
I have an import/export process reading a ~250mb file which is now running out of memory when using a Web stream.
The memory is stable on v19.9.0 but grows until an
Fatal javascript OOM in MemoryChunk allocation failed during deserialization.
or aFATAL ERROR: Committing semi space failed. Allocation failed - JavaScript heap out of memory
occurs. It seems like while the stream is running, the memory usage increases. Backpressure does not help as this seems a symptom of memory growth over clock time while the stream is running. If the_ stream is prematurely stopped, the memory issue stops.Not sure what information is needed for diagnostics. What is strange is that the Heap snapshot does not show memory growing during the stream, but the memory growth is observable while running
top
.How often does it reproduce? Is there a required condition?
Every time.
What is the expected behavior? Why is that the expected behavior?
The memory should remain stable with streams using backpressure.
What do you see instead?
The process memory usage grows until an out of memory error occurs.
Additional information
No response
The text was updated successfully, but these errors were encountered: