Error call retries were exceeded

🐞 Bug report

Command (mark with an x)

• new
• build
• serve
• test
• e2e
• generate
• add
• update
• lint
• xi18n
• run
• config
• help
• version
• doc

Is this a regression?

Yes, the previous version in which this bug was not present was:

@angular/cli 8.3.20
@angular-devkit/build-angular 0.803.20

Description

A clear and concise description of the problem…

After updating to 8.3.21, when I run ‘ng build’ or ‘ng build —prod’ the build reaches the ‘Generating ES5 bundles for differential loading’ stage. It then stops outputting information, and multiple report.xxx.json files (attached) are created, approximately 45 seconds apart.

Reverting back to 8.3.20 resolves this issue.

🔬 Minimal Reproduction

🔥 Exception or Error

[error] Error: Call retries were exceeded
    at ChildProcessWorker.initialize (node_modules@angular-devkitbuild-angularnode_modulesjest-workerbuildworkersChildProcessWorker.js:193:21)
    at ChildProcessWorker.onExit (node_modules@angular-devkitbuild-angularnode_modulesjest-workerbuildworkersChildProcessWorker.js:263:12)
    at ChildProcess.emit (events.js:210:5)
    at Process.ChildProcess._handle.onexit (internal/child_process.js:272:12)

🌍 Your Environment

Angular CLI: 8.3.21
Node: 12.13.1
OS: win32 x64
Angular: 8.2.14
... animations, common, compiler, compiler-cli, core, forms
... language-service, platform-browser, platform-browser-dynamic
... router

Package                           Version
-----------------------------------------------------------
@angular-devkit/architect         0.803.21
@angular-devkit/build-angular     0.803.21
@angular-devkit/build-optimizer   0.803.21
@angular-devkit/build-webpack     0.803.21
@angular-devkit/core              8.3.20
@angular-devkit/schematics        8.3.20
@angular/cli                      8.3.21
@ngtools/webpack                  8.3.21
@schematics/angular               8.3.21
@schematics/update                0.803.21
rxjs                              6.5.3
typescript                        3.5.3
webpack                           4.39.2

Anything else relevant?

Contents of a report file:

{
  "header": {
    "reportVersion": 1,
    "event": "Allocation failed - JavaScript heap out of memory",
    "trigger": "FatalError",
    "filename": "report.20191230.175738.18688.0.001.json",
    "dumpEventTime": "2019-12-30T17:57:38Z",
    "dumpEventTimeStamp": "1577728658928",
    "processId": 18688,
    "cwd": "C:\Horizon_Local\RDT_Backlog\LandscapeWeb\LandscapeClaim\trunk\src\Rdt.Landscape.Claim.Host\ClientApp\LandscapeClaim",
    "commandLine": [
      "C:\Program Files\nodejs\node.exe",
      "C:\Horizon_Local\RDT_Backlog\LandscapeWeb\LandscapeClaim\trunk\src\Rdt.Landscape.Claim.Host\ClientApp\LandscapeClaim\node_modules\@angular-devkit\build-angular\node_modules\jest-worker\build\workers\processChild.js"
    ],
    "nodejsVersion": "v12.13.1",
    "wordSize": 64,
    "arch": "x64",
    "platform": "win32",
    "componentVersions": {
      "node": "12.13.1",
      "v8": "7.7.299.13-node.16",
      "uv": "1.33.1",
      "zlib": "1.2.11",
      "brotli": "1.0.7",
      "ares": "1.15.0",
      "modules": "72",
      "nghttp2": "1.39.2",
      "napi": "5",
      "llhttp": "1.1.4",
      "http_parser": "2.8.0",
      "openssl": "1.1.1d",
      "cldr": "35.1",
      "icu": "64.2",
      "tz": "2019c",
      "unicode": "12.1"
    },
    "release": {
      "name": "node",
      "lts": "Erbium",
      "headersUrl": "https://nodejs.org/download/release/v12.13.1/node-v12.13.1-headers.tar.gz",
      "sourceUrl": "https://nodejs.org/download/release/v12.13.1/node-v12.13.1.tar.gz",
      "libUrl": "https://nodejs.org/download/release/v12.13.1/win-x64/node.lib"
    },
    "osName": "Windows_NT",
    "osRelease": "10.0.17134",
    "osVersion": "Windows 10 Enterprise",
    "osMachine": "x86_64",
    "cpus": [
      {
        "model": "Intel(R) Core(TM) i7-6700 CPU @ 3.40GHz",
        "speed": 3408,
        "user": 5664546,
        "nice": 0,
        "sys": 3876171,
        "idle": 107558468,
        "irq": 389625
      },
      {
        "model": "Intel(R) Core(TM) i7-6700 CPU @ 3.40GHz",
        "speed": 3408,
        "user": 5153359,
        "nice": 0,
        "sys": 2473421,
        "idle": 109472218,
        "irq": 44156
      },
      {
        "model": "Intel(R) Core(TM) i7-6700 CPU @ 3.40GHz",
        "speed": 3408,
        "user": 6340406,
        "nice": 0,
        "sys": 4032359,
        "idle": 106726234,
        "irq": 55343
      },
      {
        "model": "Intel(R) Core(TM) i7-6700 CPU @ 3.40GHz",
        "speed": 3408,
        "user": 5864171,
        "nice": 0,
        "sys": 2212093,
        "idle": 109022734,
        "irq": 32281
      },
      {
        "model": "Intel(R) Core(TM) i7-6700 CPU @ 3.40GHz",
        "speed": 3408,
        "user": 6080984,
        "nice": 0,
        "sys": 3754687,
        "idle": 107263328,
        "irq": 51015
      },
      {
        "model": "Intel(R) Core(TM) i7-6700 CPU @ 3.40GHz",
        "speed": 3408,
        "user": 5027500,
        "nice": 0,
        "sys": 1923109,
        "idle": 110148390,
        "irq": 37843
      },
      {
        "model": "Intel(R) Core(TM) i7-6700 CPU @ 3.40GHz",
        "speed": 3408,
        "user": 6650718,
        "nice": 0,
        "sys": 3162640,
        "idle": 107285640,
        "irq": 47531
      },
      {
        "model": "Intel(R) Core(TM) i7-6700 CPU @ 3.40GHz",
        "speed": 3408,
        "user": 5141875,
        "nice": 0,
        "sys": 1924468,
        "idle": 110032656,
        "irq": 30203
      }
    ],
    "networkInterfaces": [
      {
        "name": "Ethernet",
        "internal": false,
        "mac": "3c:52:82:66:86:8a",
        "address": "fe80::e0b3:9450:6f17:1021",
        "netmask": "ffff:ffff:ffff:ffff::",
        "family": "IPv6",
        "scopeid": 10
      },
      {
        "name": "Ethernet",
        "internal": false,
        "mac": "3c:52:82:66:86:8a",
        "address": "172.16.4.117",
        "netmask": "255.255.248.0",
        "family": "IPv4"
      },
      {
        "name": "Loopback Pseudo-Interface 1",
        "internal": true,
        "mac": "00:00:00:00:00:00",
        "address": "::1",
        "netmask": "ffff:ffff:ffff:ffff:ffff:ffff:ffff:ffff",
        "family": "IPv6",
        "scopeid": 0
      },
      {
        "name": "Loopback Pseudo-Interface 1",
        "internal": true,
        "mac": "00:00:00:00:00:00",
        "address": "127.0.0.1",
        "netmask": "255.0.0.0",
        "family": "IPv4"
      }
    ],
    "host": "RDTW01284"
  },
  "javascriptStack": {
    "message": "No stack.",
    "stack": [
      "Unavailable."
    ]
  },
  "nativeStack": [
    {
      "pc": "0x00007ff788911729",
      "symbol": "std::basic_ostream >::operator<<+10873"
    },
    {
      "pc": "0x00007ff788915b4c",
      "symbol": "std::basic_ostream >::operator<<+28316"
    },
    {
      "pc": "0x00007ff788914b08",
      "symbol": "std::basic_ostream >::operator<<+24152"
    },
    {
      "pc": "0x00007ff788a0369b",
      "symbol": "v8::base::CPU::has_sse+37723"
    },
    {
      "pc": "0x00007ff7892082de",
      "symbol": "v8::Isolate::ReportExternalAllocationLimitReached+94"
    },
    {
      "pc": "0x00007ff7891f0321",
      "symbol": "v8::SharedArrayBuffer::Externalize+833"
    },
    {
      "pc": "0x00007ff7890bdbec",
      "symbol": "v8::internal::Heap::EphemeronKeyWriteBarrierFromCode+1436"
    },
    {
      "pc": "0x00007ff7890c8f90",
      "symbol": "v8::internal::Heap::ProtectUnprotectedMemoryChunks+1312"
    },
    {
      "pc": "0x00007ff7890c5ac4",
      "symbol": "v8::internal::Heap::PageFlagsAreConsistent+3204"
    },
    {
      "pc": "0x00007ff7890bb353",
      "symbol": "v8::internal::Heap::CollectGarbage+1283"
    },
    {
      "pc": "0x00007ff7890b9b24",
      "symbol": "v8::internal::Heap::AddRetainedMap+2356"
    },
    {
      "pc": "0x00007ff7890dadf5",
      "symbol": "v8::internal::Factory::NewFillerObject+53"
    },
    {
      "pc": "0x00007ff788e46e19",
      "symbol": "v8::internal::interpreter::JumpTableTargetOffsets::iterator::operator=+4057"
    },
    {
      "pc": "0x00007ff78963404d",
      "symbol": "v8::internal::SetupIsolateDelegate::SetupHeap+567949"
    },
    {
      "pc": "0x000001246cf93443",
      "symbol": ""
    }
  ],
  "javascriptHeap": {
    "totalMemory": 2150961152,
    "totalCommittedMemory": 2150961152,
    "usedMemory": 2129135824,
    "availableMemory": 52074808,
    "memoryLimit": 2197815296,
    "heapSpaces": {
      "read_only_space": {
        "memorySize": 262144,
        "committedMemory": 262144,
        "capacity": 261872,
        "used": 32296,
        "available": 229576
      },
      "new_space": {
        "memorySize": 2097152,
        "committedMemory": 2097152,
        "capacity": 1047488,
        "used": 212944,
        "available": 834544
      },
      "old_space": {
        "memorySize": 2031726592,
        "committedMemory": 2031726592,
        "capacity": 2016133088,
        "used": 2013024032,
        "available": 3109056
      },
      "code_space": {
        "memorySize": 1736704,
        "committedMemory": 1736704,
        "capacity": 1449632,
        "used": 1449632,
        "available": 0
      },
      "map_space": {
        "memorySize": 1576960,
        "committedMemory": 1576960,
        "capacity": 1048640,
        "used": 1048640,
        "available": 0
      },
      "large_object_space": {
        "memorySize": 113512448,
        "committedMemory": 113512448,
        "capacity": 113364728,
        "used": 113364728,
        "available": 0
      },
      "code_large_object_space": {
        "memorySize": 49152,
        "committedMemory": 49152,
        "capacity": 3552,
        "used": 3552,
        "available": 0
      },
      "new_large_object_space": {
        "memorySize": 0,
        "committedMemory": 0,
        "capacity": 1047488,
        "used": 0,
        "available": 1047488
      }
    }
  },
  "resourceUsage": {
    "userCpuSeconds": 126.578,
    "kernelCpuSeconds": 3.328,
    "cpuConsumptionPercent": 216.51,
    "maxRss": 2282307584,
    "pageFaults": {
      "IORequired": 1079275,
      "IONotRequired": 0
    },
    "fsActivity": {
      "reads": 2654,
      "writes": 109
    }
  },
  "libuv": [
  ],
  "environmentVariables": {
    REMOVED
  },
  "sharedObjects": [
    "C:\Program Files\nodejs\node.exe",
    "C:\WINDOWS\SYSTEM32\ntdll.dll",
    "C:\WINDOWS\System32\KERNEL32.DLL",
    "C:\WINDOWS\System32\KERNELBASE.dll",
    "C:\WINDOWS\System32\WS2_32.dll",
    "C:\WINDOWS\System32\RPCRT4.dll",
    "C:\WINDOWS\SYSTEM32\dbghelp.dll",
    "C:\WINDOWS\System32\ucrtbase.dll",
    "C:\WINDOWS\System32\ADVAPI32.dll",
    "C:\WINDOWS\System32\msvcrt.dll",
    "C:\WINDOWS\System32\sechost.dll",
    "C:\WINDOWS\System32\USER32.dll",
    "C:\WINDOWS\System32\win32u.dll",
    "C:\WINDOWS\System32\GDI32.dll",
    "C:\WINDOWS\System32\gdi32full.dll",
    "C:\WINDOWS\System32\msvcp_win.dll",
    "C:\WINDOWS\System32\PSAPI.DLL",
    "C:\WINDOWS\System32\CRYPT32.dll",
    "C:\WINDOWS\System32\MSASN1.dll",
    "C:\WINDOWS\SYSTEM32\IPHLPAPI.DLL",
    "C:\WINDOWS\SYSTEM32\USERENV.dll",
    "C:\WINDOWS\SYSTEM32\bcrypt.dll",
    "C:\WINDOWS\System32\profapi.dll",
    "C:\WINDOWS\SYSTEM32\WINMM.dll",
    "C:\WINDOWS\SYSTEM32\WINMMBASE.dll",
    "C:\WINDOWS\System32\cfgmgr32.dll",
    "C:\WINDOWS\System32\IMM32.DLL",
    "C:\WINDOWS\System32\powrprof.dll",
    "C:\WINDOWS\SYSTEM32\CRYPTBASE.DLL",
    "C:\WINDOWS\System32\bcryptPrimitives.dll",
    "C:\WINDOWS\system32\uxtheme.dll",
    "C:\WINDOWS\System32\combase.dll",
    "C:\WINDOWS\system32\mswsock.dll",
    "C:\WINDOWS\System32\kernel.appcore.dll",
    "C:\WINDOWS\System32\NSI.dll",
    "C:\WINDOWS\SYSTEM32\dhcpcsvc6.DLL",
    "C:\WINDOWS\SYSTEM32\dhcpcsvc.DLL",
    "C:\WINDOWS\system32\napinsp.dll",
    "C:\WINDOWS\system32\pnrpnsp.dll",
    "C:\WINDOWS\system32\NLAapi.dll",
    "C:\WINDOWS\SYSTEM32\DNSAPI.dll",
    "C:\WINDOWS\System32\winrnr.dll",
    "C:\WINDOWS\System32\wshbth.dll"
  ]
}

Call retries were exceeded. Allocation failed — JavaScript heap out of memory error on build #16515

Command (mark with an x )

Is this a regression?

@angular/cli 8.3.20
@angular-devkit/build-angular 0.803.20

Description

After updating to 8.3.21, when I run ‘ng build’ or ‘ng build —prod’ the build reaches the ‘Generating ES5 bundles for differential loading’ stage. It then stops outputting information, and multiple report.xxx.json files (attached) are created, approximately 45 seconds apart.

Reverting back to 8.3.20 resolves this issue.

🔬 Minimal Reproduction

🔥 Exception or Error

🌍 Your Environment

Anything else relevant?

Contents of a report file:

The text was updated successfully, but these errors were encountered:

Can you provide the console output of the successful build? The amount and sizes of the output files are of particular interest.
Please also provide the options used within the angular.json file that would be used for a production build of the project. This would include the options object and the production configuration object for the build` target.
Do you happen to know what the total system memory as well as the available system memory was prior to executing the build?

Also of concern is that the following are not at .21 as the other dependencies are:

Are these manually specified in the workspace’s package.json?

Thanks for the response.

Sorry to repeat, but this is failing on both debug and production environments.

However, on a successful build:

ng build —prod

ng build

angular.json

Memory
System memory = 16GB
In use = 9.3GB
Versions
The only reference to @angular-devkit is within the devDependencies

Hope this helps

I have exact same issue, need help

ES5 bundles fail to be generated with the error «Maximum call stack size exceeded». In my case, I am building an application with Ionic, which leverages ES5. This appears to have been introduced with this commit.

I have created a repository that demonstrates this bug.

Checkout https://github.com/devinshoemaker/repro-max-call-stack
npm install
ng build
If you downgrade @angular-devkit/build-angular then build will complete successfully.

npm install @angular-devkit/build-angular@0.801.2
ng build
Issues that don’t have enough info and can’t be reproduced will be closed.

ES5 bundles fail to be generated with the error «Maximum call stack size exceeded». In my case, I am building an application with Ionic, which leverages ES5. This appears to have been introduced with this commit.

I have created a repository that demonstrates this bug.

Checkout https://github.com/devinshoemaker/repro-max-call-stack
npm install
ng build
If you downgrade @angular-devkit/build-angular then build will complete successfully.

npm install @angular-devkit/build-angular@0.801.2
ng build
Issues that don’t have enough info and can’t be reproduced will be closed.

An update to this; changing the target property in tsconfig.json from es2015 to es5 results in a successful build.

FYI, changing to ES5 allowed my build to go through too

@devinshoemaker same here! changing to ES5 allowed my build to go through too.

Changing the target to es5 disables differential loading, which may not be desired in all cases.
https://angular.io/guide/deployment#differential-loading

Facing this on a CI pipeline as well. And have no desire to turn off differential builds.
Or, only disabling for a particular configuration in angular.json might be a feasible solution for me.

@AhsanAyaz you might try this workaround that was posted in a different issue: #16520 (comment)

Facing this on a CI pipeline as well. And have no desire to turn off differential builds.
Or, only disabling for a particular configuration in angular.json might be a feasible solution for me.

The above was my use-case. If you also want to disable the differential loading only for a certain configuration, you can create a new tsconfig.something.json inside the src folder, similar to tsconfig.app.json .

For my case, I created a tsconfig.devserver.json with the following content:

And then I’m just running the below script to not ruin my other builds which use optimizations and are successful at the moment:

• Fixed the problem for me 🎉
• Didn’t have to modify tsconfig.app.json 💥

It is working again for me with the latest versions (released a few hours ago):

The recently released version of the CLI (8.3.22) has several improvements to prevent excessive memory usage when processing source maps. Based on the provided reproductions, the memory usage issues were no longer present when using the new version.
For anyone experiencing memory issues, please update to the latest CLI version (currently 8.3.22 ). Also ensure that the @angular-devkit/build-angular version is at least 0.803.22 . This package contains a majority of the build processing logic. It is also recommended to use the latest version of Node.js 12 as well (currently 12.14.1 ).

If anyone is still encountering issues after ensuring these changes, please open a new issue describing the problem and if possible provide a minimal reproduction.
In addition, please be aware that Node.js has a default memory limit of

2GB and that for very large projects this may need to be increased. This can be accomplished via the following:
node —max_old_space_size=4096 node_modules/@angular/cli/bin/ng build
The 4096 value essentially represents a maximum memory usage value for the node process in megabytes. For this example, that would be 4GB of memory but can be adjusted as needed. Ensure that the system has enough physical memory to support the value chosen.

Источник

Migration issue: Call retries were exceeded #34501

Affected Package

Is this a regression?

Not sure, but I have not see this problem before.

Description

I am trying to upgrade from Angular 8.2.x to 9.0-rc7

These ran successfully:

I then tried ng build and ran into the error noted below.

This appears to be the same as #32913, which was reported as fixed in this release, but it is not.

🔬 Minimal Reproduction

While I am not able to create a minimal reproduction, I believe my actual codebase (which is open-source) is sufficient to demonstrate the issue.

From that branch, just run ng build .

🔥 Exception or Error

That log contents is:

🌍 Your Environment

Angular Version:

Anything else relevant?

Running on macOS Mojave.

The text was updated successfully, but these errors were encountered:

@msorens Thanks for submitting this issue! I just want to clarify that the issue you linked to (#32913) has been fixed since the issue was only about the migration errors similar to the followed:

The issue also mentions unrelated things about ng build no longer working. Though these things did not belong into that issue at all, since it was only about the SCSS resolution errors (which have been fixed)

The issue you are facing seems to be CLI specific, and has been tracked with angular/angular-cli#15493. I’ll close this issue since there seem to be several issues about this on the CLI repository. Please let me know if you think this should be re-opened/if you see different things. Thanks!

Источник

«Maximum call stack size exceeded» when Generating ES5 bundles #16520

Command (mark with an x )

Is this a regression?

Yes, this is a regression. Downgrading @angular-devkit/build-angular to 0.801.2 fixes the issue and ES5 bundles can be created successfully.

Description

ES5 bundles fail to be generated with the error «Maximum call stack size exceeded». In my case, I am building an application with Ionic, which leverages ES5. This appears to have been introduced with this commit.

🔬 Minimal Reproduction

I have created a repository that demonstrates this bug.

If you downgrade @angular-devkit/build-angular then build will complete successfully.

• npm install @angular-devkit/build-angular@0.801.2
• ng build

Issues that don’t have enough info and can’t be reproduced will be closed.

🔥 Exception or Error

🌍 Your Environment

The text was updated successfully, but these errors were encountered:

@devinshoemaker, thanks a lot for the repo. Will post it in other issue.

To confirm behavior, I can reproduce ng build failing.
But the following were successful:

@devinshoemaker Can you confirm the above on your machine?

@clydin, I got the same results.

@clydin I got the same results as well.

@devinshoemaker If you have some time can you try one more thing? Add the following source map options to the build target options object (note the vendor: true part) and try an ng build :

@clydin adding that to my angular.json resulted in a successful build.

@devinshoemaker If you have some time can you try one more thing? Add the following source map options to the build target options object (note the vendor: true part) and try an ng build :

This worked for me too, But I have no idea why.

Your other solution works as well: #16515 (comment)

Источник

^ 2.3.5/3.0.0: Call retries were exceeded #262

Operating System: macOS
Node Version: 10.17.0
NPM Version: 6.11.3
webpack Version: 4.43.0
terser-webpack-plugin Version: 2.3.7.

Expected Behavior
Shouldn’t error out.

Actual Behavior/ Error

1] [pc=0xae436d61038](this=0x087a881826f1 ) 3: arguments adaptor frame: 1->0 4: /* anonymous */(aka /* anonymous */) [0x87a0d802aa1] [/Users/nitinkp. 2: 0x10003b8d0 node_module_register [/usr/local/Cellar/node@10/10.17.0/bin/node] 3: 0x10003ba91 node::OnFatalError(char const*, char const*) [/usr/local/Cellar/node@10/10.17.0/bin/node] 4: 0x100178d87 v8::Utils::ReportOOMFailure(v8::internal::Isolate*, char const*, bool) [/usr/local/Cellar/node@10/10.17.0/bin/node] 5: 0x100178d29 v8::internal::V8::FatalProcessOutOfMemory(v8::internal::Isolate*, char const*, bool) [/usr/local/Cellar/node@10/10.17.0/bin/node] 6: 0x10042d29c v8::internal::Heap::UpdateSurvivalStatistics(int) [/usr/local/Cellar/node@10/10.17.0/bin/node] 7: 0x10042eed9 v8::internal::Heap::CheckIneffectiveMarkCompact(unsigned long, double) [/usr/local/Cellar/node@10/10.17.0/bin/node] 8: 0x10042c576 v8::internal::Heap::PerformGarbageCollection(v8::internal::GarbageCollector, v8::GCCallbackFlags) [/usr/local/Cellar/node@10/10.17.0/bin/node] 9: 0x10042b387 v8::internal::Heap::CollectGarbage(v8::internal::AllocationSpace, v8::internal::GarbageCollectionReason, v8::GCCallbackFlags) [/usr/local/Cellar/node@10/10.17.0/bin/node] 10: 0x1004339ae v8::internal::Heap::AllocateRawWithLigthRetry(int, v8::internal::AllocationSpace, v8::internal::AllocationAlignment) [/usr/local/Cellar/node@10/10.17.0/bin/node] 11: 0x1004339f8 v8::internal::Heap::AllocateRawWithRetryOrFail(int, v8::internal::AllocationSpace, v8::internal::AllocationAlignment) [/usr/local/Cellar/node@10/10.17.0/bin/node] 12: 0x1004142e7 v8::internal::Factory::NewFillerObject(int, bool, v8::internal::AllocationSpace) [/usr/local/Cellar/node@10/10.17.0/bin/node] 13: 0x1005ee60d v8::internal::Runtime_AllocateInNewSpace(int, v8::internal::Object**, v8::internal::Isolate*) [/usr/local/Cellar/node@10/10.17.0/bin/node] 14: 0xae43685be3d 15: 0xae43685d1ff «>

ERROR in js/app.js from Terser
Error: Call retries were exceeded
at ChildProcessWorker.initialize (/repo/node_modules/jest-worker/build/workers/ChildProcessWorker.js:191:21)
at ChildProcessWorker._onExit (/repo/node_modules/jest-worker/build/workers/ChildProcessWorker.js:268:12)
at ChildProcess.emit (events.js:198:13)
at ChildProcess.EventEmitter.emit (domain.js:448:20)
at Process.ChildProcess._handle.onexit (internal/child_process.js:248:12)

I didn’t encounter this error until I run npm clean cache / npm install when the terser-webpack-plugin updated to 2.3.7 from 2.3.6.
I did some search in the stack overflow and also checked a few closed issues but none of them seems to be working.
Even updated & downgraded the package to the latest release i.e 3.0 & 2.1 but the result.

My Webpack config

I also tried to give the parallel property a number value: 2 / os.cpus().length;() -1.
but this also didn’t work.
FYI — CPU’s length is 4. No CircleCi configuration.
Even tried setting nodemon —max_old_space_size=4096 src/server/index.js.

there are other folks having the same problem but raised an issue with create-react-app repo which I found while searching a solution for this issue.
facebook/create-react-app#8320

let me know if I need to add/update something to overcome this problem.

The text was updated successfully, but these errors were encountered:

Источник

WebpackError: Call retries were exceeded & Window is not defined #765

My project is based on gatsby-website. When I run gatsby build command it will gives following error.

ReferenceError: window is not defined
at D:Projectpublicrender-page.js:40343:3
at new Promise ()
at Object../node_modules/pdfjs-dist/lib/web/ui_utils.js (D:Projectpublicrender-page.js:40342:26)
at webpack_require (D:Projectpublicrender-page.js:48610:42)
at Object../node_modules/pdfjs-dist/lib/web/pdf_link_service.js (D:Projectpublicrender-page.js:39345:17)
at webpack_require (D:Projectpublicrender-page.js:48610:42)
at Module../node_modules/react-pdf/dist/esm/LinkService.js (D:Projectpublicrender-page.js:44030:93)
at webpack_require (D:Projectpublicrender-page.js:48610:42)
at Module../node_modules/react-pdf/dist/esm/Document.js (D:Projectpublicrender-page.js:43465:71)
at webpack_require (D:Projectpublicrender-page.js:48610:42)
at Module../node_modules/react-pdf/dist/esm/entry.webpack.js (D:Projectpublicrender-page.js:46496:67)
at webpack_require (D:Projectpublicrender-page.js:48610:42)
at Module../src/routes/default/index.js (D:Projectpublicrender-page.js:7404:90)
at webpack_require (D:Projectpublicrender-page.js:48610:42)
at Object../.cache/this_is_virtual_fs_path/$virtual/sync-requires.js (D:Projectpublicrender-page.js:6740:
116)
failed Building static HTML for pages — 1.672s

Building static HTML failed

See our docs page for more info on this error: https://gatsby.dev/debug-html

10 |
11 | export default function _createClass(Constructor, protoProps, staticProps) <

12 | if (protoProps) _defineProperties(Constructor.prototype, protoProps);
| ^
13 | if (staticProps) _defineProperties(Constructor, staticProps);
14 | return Constructor;
15 | >

WebpackError: Call retries were exceeded

I used react-pdf version react-pdf 5.2.0.

and import < Document, Page >from ‘react-pdf/dist/esm/entry.webpack’;

I cannot get the issue. I checked everywhere, I used window !== ‘undefined’ && window.xyz condition.
Before 10 days it is working perfectly and Now it is not working.

The text was updated successfully, but these errors were encountered:

Источник

Migration issue: Call retries were exceeded #34501

Comments

msorens commented Dec 19, 2019

🐞 bug report

Affected Package

Is this a regression?

Not sure, but I have not see this problem before.

Description

I am trying to upgrade from Angular 8.2.x to 9.0-rc7

These ran successfully:

I then tried ng build and ran into the error noted below.

This appears to be the same as #32913, which was reported as fixed in this release, but it is not.

🔬 Minimal Reproduction

While I am not able to create a minimal reproduction, I believe my actual codebase (which is open-source) is sufficient to demonstrate the issue.

From that branch, just run ng build .

🔥 Exception or Error

That log contents is:

🌍 Your Environment

Angular Version:

Anything else relevant?

Running on macOS Mojave.

The text was updated successfully, but these errors were encountered:

devversion commented Dec 19, 2019

@msorens Thanks for submitting this issue! I just want to clarify that the issue you linked to (#32913) has been fixed since the issue was only about the migration errors similar to the followed:

The issue also mentions unrelated things about ng build no longer working. Though these things did not belong into that issue at all, since it was only about the SCSS resolution errors (which have been fixed)

The issue you are facing seems to be CLI specific, and has been tracked with angular/angular-cli#15493. I’ll close this issue since there seem to be several issues about this on the CLI repository. Please let me know if you think this should be re-opened/if you see different things. Thanks!

Источник

Call retries were exceeded. Allocation failed — JavaScript heap out of memory error on build #16515

Comments

jrdutton commented Dec 30, 2019

🐞 Bug report

Command (mark with an x )

• new
• build
• serve
• test
• e2e
• generate
• add
• update
• lint
• xi18n
• run
• config
• help
• version
• doc

Is this a regression?

@angular/cli 8.3.20
@angular-devkit/build-angular 0.803.20

Description

After updating to 8.3.21, when I run ‘ng build’ or ‘ng build —prod’ the build reaches the ‘Generating ES5 bundles for differential loading’ stage. It then stops outputting information, and multiple report.xxx.json files (attached) are created, approximately 45 seconds apart.

Reverting back to 8.3.20 resolves this issue.

🔬 Minimal Reproduction

🔥 Exception or Error

🌍 Your Environment

Anything else relevant?

Contents of a report file:

The text was updated successfully, but these errors were encountered:

clydin commented Dec 30, 2019

Can you provide the console output of the successful build? The amount and sizes of the output files are of particular interest.
Please also provide the options used within the angular.json file that would be used for a production build of the project. This would include the options object and the production configuration object for the build` target.
Do you happen to know what the total system memory as well as the available system memory was prior to executing the build?

Also of concern is that the following are not at .21 as the other dependencies are:

Are these manually specified in the workspace’s package.json?

jrdutton commented Dec 30, 2019

Thanks for the response.

Sorry to repeat, but this is failing on both debug and production environments.

However, on a successful build:

ng build —prod

ng build

angular.json

Memory
System memory = 16GB
In use = 9.3GB
Versions
The only reference to @angular-devkit is within the devDependencies

Hope this helps

vaibhavarora14 commented Dec 31, 2019

I have exact same issue, need help

alan-agius4 commented Dec 31, 2019 •

ES5 bundles fail to be generated with the error «Maximum call stack size exceeded». In my case, I am building an application with Ionic, which leverages ES5. This appears to have been introduced with this commit.

I have created a repository that demonstrates this bug.

Checkout https://github.com/devinshoemaker/repro-max-call-stack
npm install
ng build
If you downgrade @angular-devkit/build-angular then build will complete successfully.

npm install @angular-devkit/build-angular@0.801.2
ng build
Issues that don’t have enough info and can’t be reproduced will be closed.

devinshoemaker commented Jan 5, 2020

ES5 bundles fail to be generated with the error «Maximum call stack size exceeded». In my case, I am building an application with Ionic, which leverages ES5. This appears to have been introduced with this commit.

I have created a repository that demonstrates this bug.

Checkout https://github.com/devinshoemaker/repro-max-call-stack
npm install
ng build
If you downgrade @angular-devkit/build-angular then build will complete successfully.

npm install @angular-devkit/build-angular@0.801.2
ng build
Issues that don’t have enough info and can’t be reproduced will be closed.

An update to this; changing the target property in tsconfig.json from es2015 to es5 results in a successful build.

jrdutton commented Jan 6, 2020

FYI, changing to ES5 allowed my build to go through too

shnave commented Jan 6, 2020

@devinshoemaker same here! changing to ES5 allowed my build to go through too.

jessorlisa commented Jan 7, 2020

Changing the target to es5 disables differential loading, which may not be desired in all cases.
https://angular.io/guide/deployment#differential-loading

AhsanAyaz commented Jan 7, 2020

Facing this on a CI pipeline as well. And have no desire to turn off differential builds.
Or, only disabling for a particular configuration in angular.json might be a feasible solution for me.

devinshoemaker commented Jan 7, 2020

@AhsanAyaz you might try this workaround that was posted in a different issue: #16520 (comment)

AhsanAyaz commented Jan 7, 2020

Facing this on a CI pipeline as well. And have no desire to turn off differential builds.
Or, only disabling for a particular configuration in angular.json might be a feasible solution for me.

The above was my use-case. If you also want to disable the differential loading only for a certain configuration, you can create a new tsconfig.something.json inside the src folder, similar to tsconfig.app.json .

For my case, I created a tsconfig.devserver.json with the following content:

And then I’m just running the below script to not ruin my other builds which use optimizations and are successful at the moment:

• Fixed the problem for me 🎉
• Didn’t have to modify tsconfig.app.json 💥

jessorlisa commented Jan 9, 2020

It is working again for me with the latest versions (released a few hours ago):

clydin commented Jan 9, 2020

The recently released version of the CLI (8.3.22) has several improvements to prevent excessive memory usage when processing source maps. Based on the provided reproductions, the memory usage issues were no longer present when using the new version.
For anyone experiencing memory issues, please update to the latest CLI version (currently 8.3.22 ). Also ensure that the @angular-devkit/build-angular version is at least 0.803.22 . This package contains a majority of the build processing logic. It is also recommended to use the latest version of Node.js 12 as well (currently 12.14.1 ).

If anyone is still encountering issues after ensuring these changes, please open a new issue describing the problem and if possible provide a minimal reproduction.
In addition, please be aware that Node.js has a default memory limit of

2GB and that for very large projects this may need to be increased. This can be accomplished via the following:
node —max_old_space_size=4096 node_modules/@angular/cli/bin/ng build
The 4096 value essentially represents a maximum memory usage value for the node process in megabytes. For this example, that would be 4GB of memory but can be adjusted as needed. Ensure that the system has enough physical memory to support the value chosen.

Источник

error: node_modulesaws-sdkdistaws-sdk-react-native.js: Call retries were exceeded #3990

Comments

shakeel0581 commented Dec 15, 2021

Confirm by changing [ ] to [x] below to ensure that it’s a bug:

• I’ve gone through Developer Guide and API reference
• I’ve checked AWS Forums and StackOverflow for answers
• I’ve searched for previous similar issues and didn’t find any solution
• This is an issue with version 2.x of the SDK

Describe the bug
A clear and concise description of what the bug is.

Is the issue in the browser/Node.js?
Browser/Node.js

If on Node.js, are you running this on AWS Lambda?

Details of the browser/Node.js version
Paste output of npx envinfo —browsers or node -v

SDK version number
Example: v2.466.0

• For browsers, the SDK version number is in the script tag
• For Node.js, get SDK version by
  • running command npm list aws-sdk from your root directory
  • printing the output of console.log(AWS.VERSION) in your code where AWS = require(«aws-sdk»);
  • if running on Lambda and using SDK provided by Lambda runtime, you can find the SDK versions here

To Reproduce (observed behavior)
Steps to reproduce the behavior (please share code or minimal repo)

Expected behavior
A clear and concise description of what you expected to happen.

Screenshots
If applicable, add screenshots to help explain your problem.

Additional context
Add any other context about the problem here.

The text was updated successfully, but these errors were encountered:

Источник

WebpackError: Call retries were exceeded & Window is not defined #765

Comments

abhaybriskteq commented Apr 13, 2021 •

My project is based on gatsby-website. When I run gatsby build command it will gives following error.

ReferenceError: window is not defined
at D:Projectpublicrender-page.js:40343:3
at new Promise ()
at Object../node_modules/pdfjs-dist/lib/web/ui_utils.js (D:Projectpublicrender-page.js:40342:26)
at webpack_require (D:Projectpublicrender-page.js:48610:42)
at Object../node_modules/pdfjs-dist/lib/web/pdf_link_service.js (D:Projectpublicrender-page.js:39345:17)
at webpack_require (D:Projectpublicrender-page.js:48610:42)
at Module../node_modules/react-pdf/dist/esm/LinkService.js (D:Projectpublicrender-page.js:44030:93)
at webpack_require (D:Projectpublicrender-page.js:48610:42)
at Module../node_modules/react-pdf/dist/esm/Document.js (D:Projectpublicrender-page.js:43465:71)
at webpack_require (D:Projectpublicrender-page.js:48610:42)
at Module../node_modules/react-pdf/dist/esm/entry.webpack.js (D:Projectpublicrender-page.js:46496:67)
at webpack_require (D:Projectpublicrender-page.js:48610:42)
at Module../src/routes/default/index.js (D:Projectpublicrender-page.js:7404:90)
at webpack_require (D:Projectpublicrender-page.js:48610:42)
at Object../.cache/this_is_virtual_fs_path/$virtual/sync-requires.js (D:Projectpublicrender-page.js:6740:
116)
failed Building static HTML for pages — 1.672s

Building static HTML failed

See our docs page for more info on this error: https://gatsby.dev/debug-html

10 |
11 | export default function _createClass(Constructor, protoProps, staticProps) <

12 | if (protoProps) _defineProperties(Constructor.prototype, protoProps);
| ^
13 | if (staticProps) _defineProperties(Constructor, staticProps);
14 | return Constructor;
15 | >

WebpackError: Call retries were exceeded

I used react-pdf version react-pdf 5.2.0.

and import < Document, Page >from ‘react-pdf/dist/esm/entry.webpack’;

I cannot get the issue. I checked everywhere, I used window !== ‘undefined’ && window.xyz condition.
Before 10 days it is working perfectly and Now it is not working.

The text was updated successfully, but these errors were encountered:

Источник

Nextjs Build Failed with type: ‘WorkerError’ #38324

Comments

m3rashid commented Jul 5, 2022

Verify canary release

• I verified that the issue exists in the latest Next.js canary release

Provide environment information

Operating System:
Platform: linux
Arch: x64
Version: #43-Ubuntu SMP Wed Jun 15 12:54:21 UTC 2022
Binaries:
Node: 16.15.0
npm: 8.5.5
Yarn: 1.22.18
pnpm: N/A
Relevant packages:
next: 12.2.1-canary.2
eslint-config-next: 12.1.6
react: 18.2.0
react-dom: 18.2.0

What browser are you using? (if relevant)

Using Brave (But it is irrelevent imo because error in building, dev works fine)

How are you deploying your application? (if relevant)

not deployed yet

Describe the Bug

Build fails with the following error messages on the console

Expected Behavior

Build create Successfully

Link to reproduction

To Reproduce

run the following command

The text was updated successfully, but these errors were encountered:

m3rashid commented Jul 5, 2022

I have checked in the next@canary version also,
Same error persists in canary version also
Wrote this in the initial issue also

Cahmoraes commented Jul 7, 2022 •

I’m having the same problem.

Operating System:
Platform: Win 10
Arch: x64
Binaries:
Node: 16.14.2
npm: 8.5.5
Yarn: 1.22.18
pnpm: N/A
Relevant packages:
next: 12.2.0
eslint-config-next: 12.2.0
react: 18.2.0
react-dom: 18.2.0

This comment was marked as off-topic.

omeersari commented Jul 10, 2022 •

Same error, but in my local when I yarn build , it works, however when I try to deploy my app in vercel, it gives me this error.

balazsorban44 commented Jul 11, 2022

I traced it back to some axios -related issues.

Given this code in pages/[slug].js

The error appears.

ryanmr commented Jul 22, 2022

I recently encountered this with a project on yarn build with next latest (which at this 12.2.2), just as balazsorban44 mentioned. It was occurring in my ci runner, and I realized someone else on the team was using getStaticPaths referencing an api route that wasn’t available in ci. For some reason though, getStaticPaths wanted to serialize the error that was produced (which was stemming from axios not being to reach the api), and the serialization failed.

Источник

Issue

I am facing an exception while ng build (generating ES5 bundles for differential loading…)

An unhandled exception occured: Call retires were exceeded

Used versions:

• Angular-CLI: 8.3.20
• Angular: 8.2.7
• Node: 12.12.1

Also in logs, it is mentioned

[error] Error: Call retries were exceeded at ChildProcessWorker.initialize

Solution

Update 10.02.2019

This was a problem of the @angular/cli. Updating the version to >= 8.3.22 should fix the issue: see this comment in #16515

ORIGINAL

Basically the build process is running out of memory: see related angular-cli issues #15493, #16515

The recommended remedy is to:

• update node to the latest version e.g. 12.14.0
• increase the memory for the build process:
  • in your package.json change the "build" script to: node --max_old_space_size=4096 node_modules/@angular/cli/bin/ng build
  • in this case the memory is increased to 4GB
    depending on the size of your project you may need more

As a quick workaround it could also work to use older versions of angular/cli and build-angular:

"devDependencies": {
    "@angular-devkit/build-angular": "0.803.20",
    "@angular/cli": "8.3.20",

Another workaround is to disable differential-loading (i.e. skip generation of ES5 bundles), if you want this. Then the build-process will need less memory and may work.

Answered By — TmTron