OOMErrorHandler #5
Description
我在服务器部署的时候出现了OOM，这个WebUI这么大的吗！（2U/1G）
下面是Log File
○ Compiling /chat ...
<--- Last few GCs --->
[2399:0x1c39b000] 346588 ms: Scavenge 464.3 (485.1) -> 463.9 (489.6) MB, pooled: 0 MB, 6.54 / 0.00 ms (average mu = 0.545, current mu = 0.548) allocation failure;
[2399:0x1c39b000] 348189 ms: Mark-Compact 466.7 (489.6) -> 461.8 (491.4) MB, pooled: 0 MB, 1507.17 / 0.00 ms (average mu = 0.425, current mu = 0.286) allocation failure; scavenge might not succeed
<--- JS stacktrace --->
FATAL ERROR: Reached heap limit Allocation failed - JavaScript heap out of memory
----- Native stack trace -----
1: 0xe36196 node::OOMErrorHandler(char const*, v8::OOMDetails const&) [next-server]
2: 0x123f4a0 v8::Utils::ReportOOMFailure(v8::internal::Isolate*, char const*, v8::OOMDetails const&) [next-server]
3: 0x123f777 v8::internal::V8::FatalProcessOutOfMemory(v8::internal::Isolate*, char const*, v8::OOMDetails const&) [next-server]
4: 0x146d1a5 [next-server]
5: 0x1486a19 v8::internal::Heap::CollectGarbage(v8::internal::AllocationSpace, v8::internal::GarbageCollectionReason, v8::GCCallbackFlags) [next-server]
6: 0x145b0e8 v8::internal::HeapAllocator::AllocateRawWithLightRetrySlowPath(int, v8::internal::AllocationType, v8::internal::AllocationOrigin, v8::internal::AllocationAlignment) [next-server]
7: 0x145c015 v8::internal::HeapAllocator::AllocateRawWithRetryOrFailSlowPath(int, v8::internal::AllocationType, v8::internal::AllocationOrigin, v8::internal::AllocationAlignment) [next-server]
8: 0x1434cee v8::internal::Factory::NewFillerObject(int, v8::internal::AllocationAlignment, v8::internal::AllocationType, v8::internal::AllocationOrigin) [next-server]
9: 0x18962ec v8::internal::Runtime_AllocateInYoungGeneration(int, unsigned long*, v8::internal::Isolate*) [next-server]
10: 0x1df2476 [next-server]