We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
run with RPC_CACHE_CAPACITY=100
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
The text was updated successfully, but these errors were encountered:
still has the issue on v2.9.5. It's scavenge might not succeed this time
scavenge might not succeed
<--- 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
Sorry, something went wrong.
might be the same issue #1008 seems we have some other memory leak issue other than the storage query cache
Successfully merging a pull request may close this issue.
run with
RPC_CACHE_CAPACITY=100
The text was updated successfully, but these errors were encountered: