-
Notifications
You must be signed in to change notification settings - Fork 2.5k
长时间运行经常出现内存 错误,导致进程崩溃 #4399
Copy link
Copy link
Closed
Labels
category/performancePerformance and optimizationPerformance and optimizationduplicateIssue duplicates an existing report.Issue duplicates an existing report.scope/memory-usageMemory consumptionMemory consumptionscope/session-managementSession state and persistenceSession state and persistencetype/bugSomething isn't working as expectedSomething isn't working as expected
Metadata
Metadata
Assignees
Labels
category/performancePerformance and optimizationPerformance and optimizationduplicateIssue duplicates an existing report.Issue duplicates an existing report.scope/memory-usageMemory consumptionMemory consumptionscope/session-managementSession state and persistenceSession state and persistencetype/bugSomething isn't working as expectedSomething isn't working as expected
Type
Fields
Give feedbackNo fields configured for issues without a type.
What happened?
长时间运行经常出现内存 错误,导致进程崩溃
<--- Last few GCs --->
[1639:0x7143000] 13250378 ms: Scavenge (interleaved) 4082.3 (4100.5) -> 4075.4 (4101.2) MB, pooled: 0 MB, 9.52 / 0.04 ms (average mu = 0.376, current mu = 0.376) allocation failure;
[1639:0x7143000] 13251655 ms: Mark-Compact (reduce) 4085.9 (4104.2) -> 4073.2 (4086.5) MB, pooled: 0 MB, 199.68 / 4.00 ms (+ 825.5 ms in 164 steps since start of marking, biggest step 5.5 ms, walltime since start of marking 1149 ms) (average mu = 0.348,
FATAL ERROR: Ineffective mark-compacts near heap limit Allocation failed - JavaScript heap out of memory
----- Native stack trace -----
1: 0x735eec node::OOMErrorHandler(char const*, v8::OOMDetails const&) [/usr/bin/node]
2: 0xbafbd0 [/usr/bin/node]
3: 0xbafcbf [/usr/bin/node]
4: 0xe49875 [/usr/bin/node]
5: 0xe498a2 [/usr/bin/node]
6: 0xe49b9a [/usr/bin/node]
7: 0xe5a89a [/usr/bin/node]
8: 0xe5ec40 [/usr/bin/node]
9: 0x18f3681 [/usr/bin/node]
What did you expect to happen?
长时间运行经常出现内存 错误,导致进程崩溃
Client information
长时间运行经常出现内存 错误,导致进程崩溃
Login information
No response
Anything else we need to know?
No response