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
A lot of the nodejs api containers are exiting with heap out of memory errors. Look for memory leak or increase memory accordingly
References and additional details
<--- Last few GCs --->
[1:0x7fa92b6c0290] 101476604 ms: Mark-sweep (reduce) 244.8 (258.2) -> 244.8 (258.2) MB, 316.7 / 0.0 ms (+ 270.3 ms in 14 steps since start of marking, biggest step 98.3 ms, walltime since start of marking 590 ms) (average mu = 0.291, current mu = 0.175) [1:0x7fa92b6c0290] 101477024 ms: Mark-sweep (reduce) 245.7 (258.2) -> 245.6 (259.2) MB, 419.0 / 0.0 ms (average mu = 0.181, current mu = 0.003) allocation failure; scavenge might not succeed
<--- JS stacktrace --->
FATAL ERROR: Reached heap limit Allocation failed - JavaScript heap out of memory
Acceptance Criteria
Fatal heap errors are resolved
Need By Date
No response
Screenshots/Mockups
No response
Estimated effort
No response
The text was updated successfully, but these errors were encountered:
This may no longer be an issue as of #908. Going to leave open for now and keep an eye out for restarts over the next week or slow to determine if we can close this or not.
Overview
A lot of the nodejs api containers are exiting with heap out of memory errors. Look for memory leak or increase memory accordingly
References and additional details
Acceptance Criteria
Need By Date
No response
Screenshots/Mockups
No response
Estimated effort
No response
The text was updated successfully, but these errors were encountered: