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.

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 on v2.9.4 #1059

Open
zjb0807 opened this issue Nov 28, 2024 · 2 comments · Fixed by #1051
Open

JavaScript heap out of memory on v2.9.4 #1059

zjb0807 opened this issue Nov 28, 2024 · 2 comments · Fixed by #1051

Comments

@zjb0807
Copy link
Member

zjb0807 commented Nov 28, 2024

run with RPC_CACHE_CAPACITY=100

<--- Last few GCs --->

[1:0x7fc15179c020] 462423328 ms: Scavenge 1946.4 (2080.5) -> 1940.8 (2080.3) MB, 10.0 / 0.0 ms  (average mu = 0.921, current mu = 0.917) allocation failure;
[1:0x7fc15179c020] 462424307 ms: Scavenge 1947.9 (2080.3) -> 1942.2 (2080.3) MB, 13.0 / 0.0 ms  (average mu = 0.921, current mu = 0.917) allocation failure;
[1:0x7fc15179c020] 462426302 ms: Scavenge 1949.6 (2080.9) -> 1943.3 (2096.5) MB, 15.0 / 0.0 ms  (average mu = 0.921, current mu = 0.917) task;


<--- JS stacktrace --->

FATAL ERROR: Reached heap limit Allocation failed - JavaScript heap out of memory
@zjb0807
Copy link
Member Author

zjb0807 commented Dec 16, 2024

still has the issue on v2.9.5. It's scavenge might not succeed this time

<--- Last few GCs --->

[1:0x7f557299e0b0] 420153155 ms: Mark-sweep 1964.8 (2080.4) -> 1949.3 (2081.4) MB, 3637.3 / 0.0 ms  (average mu = 0.153, current mu = 0.047) allocation failure; scavenge might not succeed
[1:0x7f557299e0b0] 420156874 ms: Mark-sweep 1965.4 (2081.4) -> 1948.5 (2081.2) MB, 3556.4 / 0.0 ms  (average mu = 0.100, current mu = 0.044) allocation failure; scavenge might not succeed


<--- JS stacktrace --->

FATAL ERROR: Ineffective mark-compacts near heap limit Allocation failed - JavaScript heap out of memory

@zjb0807 zjb0807 reopened this Dec 16, 2024
@shunjizhan
Copy link
Collaborator

might be the same issue #1008
seems we have some other memory leak issue other than the storage query cache

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants