You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Linux 5.15.167.4-microsoft-standard-WSL2 #1 SMP Tue Nov 5 00:21:55 UTC 2024 x86_64 x86_64 x86_64 GNU/Linux
Subsystem
v8
What steps will reproduce the bug?
Run the below script with --expose-gc.
Wait for some time.
Check the automatically generated heap snapshots.
Inspect the following path in the snapshots:
(system) > system / NativeContext > retained_maps :: system / WeakArrayList
Observe that its size keeps increasing over time.
Note:
The increase is gradual, so it may take several hours to see a significant difference.
However, even within a shorter period, a steady increase should still be observable.
How often does it reproduce? Is there a required condition?
It reproduces consistently.
What is the expected behavior? Why is that the expected behavior?
RetainedMaps size should remain stable over time.
What do you see instead?
The size of RetainedMaps (visible in heap snapshots under (system) > system / NativeContext > retained_maps :: system / WeakArrayList) keeps increasing over time.
This increase is gradual but persistent, leading to higher memory consumption over extended runtimes.
Eventually, this could result in performance degradation or excessive memory usage.
Below are screenshots showing the memory usage: v22.14.0
Version
v22.14.0
Platform
Subsystem
v8
What steps will reproduce the bug?
--expose-gc
.(system) > system / NativeContext > retained_maps :: system / WeakArrayList
Note:
The increase is gradual, so it may take several hours to see a significant difference.
However, even within a shorter period, a steady increase should still be observable.
How often does it reproduce? Is there a required condition?
It reproduces consistently.
What is the expected behavior? Why is that the expected behavior?
RetainedMaps size should remain stable over time.
What do you see instead?
Eventually, this could result in performance degradation or excessive memory usage.
Below are screenshots showing the memory usage:
v22.14.0
v22.14.0 (with the patch applied)
Additional information
e5a29df7b41416de67730d2968c61745b54be66c
V8 Issue 398528460
The text was updated successfully, but these errors were encountered: