【问题标题】:Angular build causing an error.- FATAL ERROR: Ineffective mark-compacts near heap limit Allocation failed - JavaScript heap out of memoryAngular 构建导致错误。 - 致命错误:无效标记压缩接近堆限制分配失败 - JavaScript 堆内存不足
【发布时间】:2020-09-10 14:30:30
【问题描述】:

当我尝试执行时

ng build my.sample.application --prod=false --configuration=dev

我收到如下所示的错误。为了克服这个问题,我已经执行了

node --max_old_space_size=15000

命令也是,但问题仍然存在。

错误

致命错误:接近堆限制的无效标记压缩分配失败 - JavaScript 堆内存不足
1: 00007FF6F564094F napi_wrap+124431
2: 00007FF6F55E2696 v8::base::CPU::has_sse+34502
3: 00007FF6F55E3356 v8::base::CPU::has_sse+37766
4: 00007FF6F5DE6F4E v8::Isolate::ReportExternalAllocationLimitReached+94
5: 00007FF6F5DCEF91 v8::SharedArrayBuffer::Externalize+833
6: 00007FF6F5C9C85C v8::internal::Heap::EphemeronKeyWriteBarrierFromCode+1436
7: 00007FF6F5CA7C00 v8::internal::Heap::ProtectUnprotectedMemoryChunks+1312
8: 00007FF6F5CA4734 v8::internal::Heap::PageFlagsAreConsistent+3204
9: 00007FF6F5C99FC3 v8::internal::Heap::CollectGarbage+1283
10: 00007FF6F5C98794 v8::internal::Heap::AddRetainedMap+2356
11: 00007FF6F5CC0787 v8::internal::Factory::NewRawTwoByteString+87
12: 00007FF6F5AE797C v8::internal::String::SlowFlatten+492
13: 00007FF6F59B110F unibrow::Utf8::EncodeOneByte+687
14: 00007FF6F5DF13A6 v8::String::Utf8Length+22
15: 00007FF6F55FCE0C v8::internal::Malloced::operator delete+14476
16: 00007FF6F5D9B150 v8::internal::Builtins::builtin_handle+325536
17: 00007FF6F5D9A697 v8::internal::Builtins::builtin_handle+322791
18: 00007FF6F5D9A9D8 v8::internal::Builtins::builtin_handle+323624
19: 00007FF6F5D9A7DE v8::internal::Builtins::builtin_handle+323118
20: 00007FF6F6212D6D v8::internal::SetupIsolateDelegate::SetupHeap+568205
21: 00007FF6F61927FC v8::internal::SetupIsolateDelegate::SetupHeap+42524
22: 00007FF6F618BBAC v8::internal::SetupIsolateDelegate::SetupHeap+14796
23: 00007FF6F61927FC v8::internal::SetupIsolateDelegate::SetupHeap+42524
24: 00007FF6F61927FC v8::internal::SetupIsolateDelegate::SetupHeap+42524
25: 00007FF6F61927FC v8::internal::SetupIsolateDelegate::SetupHeap+42524
26: 00007FF6F61927FC v8::internal::SetupIsolateDelegate::SetupHeap+42524
27: 00007FF6F61927FC v8::internal::SetupIsolateDelegate::SetupHeap+42524
28: 00007FF6F618BBAC v8::internal::SetupIsolateDelegate::SetupHeap+14796
29: 00007FF6F61927FC v8::internal::SetupIsolateDelegate::SetupHeap+42524
30: 00007FF6F61927FC v8::internal::SetupIsolateDelegate::SetupHeap+42524
31: 00007FF6F61927FC v8::internal::SetupIsolateDelegate::SetupHeap+42524
32: 00007FF6F61927FC v8::internal::SetupIsolateDelegate::SetupHeap+42524
33: 00007FF6F618BBAC v8::internal::SetupIsolateDelegate::SetupHeap+14796
34: 00007FF6F61927FC v8::internal::SetupIsolateDelegate::SetupHeap+42524
35: 00007FF6F618BBAC v8::internal::SetupIsolateDelegate::SetupHeap+14796
36: 00007FF6F61927FC v8::internal::SetupIsolateDelegate::SetupHeap+42524
37: 00007FF6F61927FC v8::internal::SetupIsolateDelegate::SetupHeap+42524
38: 00007FF6F61927FC v8::internal::SetupIsolateDelegate::SetupHeap+42524
39: 00007FF6F61927FC v8::internal::SetupIsolateDelegate::SetupHeap+42524
40: 00007FF6F61927FC v8::internal::SetupIsolateDelegate::SetupHeap+42524
41: 00007FF6F618BBAC v8::internal::SetupIsolateDelegate::SetupHeap+14796
42: 00007FF6F618FDB1 v8::internal::SetupIsolateDelegate::SetupHeap+31697
43: 00007FF6F618F99C v8::internal::SetupIsolateDelegate::SetupHeap+30652
44: 00007FF6F5CF4F43 v8::internal::Execution::CallWasm+1395
45: 00007FF6F5CF48C6 v8::internal::Execution::Call+182
46: 00007FF6F5DC5B3B v8::Function::Call+603
47: 00007FF6F565CA45 节点::CallbackScope::~CallbackScope+1429
48: 00007FF6F5655FE3 v8::internal::interpreter::BytecodeNode::operand_scale+179
49: 00007FF6F55DFBB3 v8::base::CPU::has_sse+23523
50: 00007FF6F55D4FE1 EVP_CIPHER_CTX_buf_noconst+200753
51: 00007FF6F568CFC7 uv_timer_stop+775
52: 00007FF6F5689AAB uv_async_send+331
53: 00007FF6F568924C uv_loop_init+1212
54: 00007FF6F5689414 uv_run+244
55: 00007FF6F55AB892 EVP_CIPHER_CTX_buf_noconst+30946
56: 00007FF6F5609263 节点::开始+275
57: 00007FF6F54C666C RC4_options+339308
58: 00007FF6F62C5D58 v8::internal::SetupIsolateDelegate::SetupHeap+1301368
59: 00007FFB974A13D2 BaseThreadInitThunk+34
60: 00007FFB977654F4 RtlUserThreadStart+52
npm 错误! Windows_NT 6.3.9600

你们能帮帮我吗?

【问题讨论】:

  • 只是为了确定,您是否使用以下命令运行它:node --max_old_space_size=15000 node_modules/@angular/cli/bin/ng build...?
  • 谢谢@David,你的建议对我有用

标签: node.js angular


【解决方案1】:

使用 "build:prod": "node --max_old_space_size=8000 ./node_modules/@angular/cli/bin/ng build --configuration=prod",在你的 package.json 文件中 1

这将告诉节点超出命令中给定大小的默认内存分配。

【讨论】:

    【解决方案2】:

    我在编译 Angular 10 时遇到了同样的问题,但在我的情况下,问题是节点版本不正确。我的节点版本是 10.15.1,一旦我切换回节点版本 13.14.0,问题就解决了。我使用 nvm(节点版本管理器)在节点版本之间切换,因此我仍然可以运行 Angular 7/8 项目而忘记将其切换回来。

    希望这可以帮助遇到同样问题的人!

    【讨论】:

      【解决方案3】:

      我遇到了类似的问题

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

      在 Package.json 中

      --max_old_space_size=4096 不应超过您的 RAM 内存,我猜这是导致此错误的原因。

       "scripts": {
          "ng": "ng",
          "start": "node --max_old_space_size=4096 node_modules/@angular/cli/bin/ng serve",
          "build": "ng build --prod",
          "test": "ng test",
          "lint": "ng lint",
          "e2e": "ng e2e",
          "bundle-report": "node --max_old_space_size=4096 node_modules/@angular/cli/bin/ng build --prod --stats-json && webpack-bundle-analyzer dist/stats.json",
          "rtl": "webpack",
        },
      

      【讨论】:

        猜你喜欢
        • 1970-01-01
        • 2019-07-15
        • 2020-09-11
        • 2020-08-05
        • 2019-07-06
        • 2020-04-17
        • 1970-01-01
        • 2021-08-27
        • 2023-03-18
        相关资源
        最近更新 更多