FATAL ERROR: CALL_AND_RETRY_LAST Allocation failed - JavaScript heap out of memory

[pocesar]

TypeScript Version: nightly (2.6.0-dev.20170912)

Code

{
  "compilerOptions": {
    "module": "system",
    "jsx": "react",
    "target": "es5",
    "moduleResolution": "node",
    "allowSyntheticDefaultImports": true,
    "newLine": "lf",
    "allowJs": false,
    "noImplicitAny": true,
    "baseUrl": "./",
    "noEmitOnError": true,
    "sourceMap": true,
    "alwaysStrict": true,
    "inlineSourceMap": false,
    "paths": {
      "*": [
        "node_modules/@types/*"
      ]
    },
    "lib": [
      "dom",
      "es2015",
      "es5"
    ]
  }
}

07:28:49 - File change detected. Starting incremental compilation...



<--- Last few GCs --->

[1592:000002842FE68000]  7027823 ms: Mark-sweep 1401.5 (1465.4) -> 1401.5 (1465.4) MB, 4599.6 / 0.0 ms  last resort


<--- JS stacktrace --->

==== JS stack trace =========================================

Security context: 0000033CF2C1CEA9 <JSObject>
    1: set [native collection.js:~247] [pc=000000C2A8FE6697](this=000000F425FBE6F1 <Map map = 000003AA6FD983B9>,p=000003A9ED17AB21
<String[9]: @Telefone>,x=000003A9ED17AB51 <Type map = 000003AA6FDC6CF9>)
    2: getLiteralType(aka getLiteralType) [C:\nodejs\node_modules\typescript\lib\tsc.js:~24883] [pc=000000C2A8D93E76](this=0000033C
F2C02241 <undefined>,value=000000CEC1A9C961 <String[8]: Telef...

FATAL ERROR: CALL_AND_RETRY_LAST Allocation failed - JavaScript heap out of memory

Expected behavior:

Not crash

Actual behavior:

TS in watch mode is randomly crashing with the above stacktrace. I can't figure out what is making it crash. I'm using vscode, but the watch mode is tsc -w -p tsconfig.json

per @sandersn recommendation (in #17112 (comment)) opening a new issue about the same error name, but different stack

[mhegazy]

@pocesar can you share your sources with us? we are open to do this by email, or sign any required NDAs.

[sandersn]

Can you also try --diagnostics to see how many types are being created when compilation does succeed?

[pocesar]

just crashed with another stacktrace

13:38:16 - File change detected. Starting incremental compilation...



<--- Last few GCs --->

[13348:000001CC04D09180]  8048988 ms: Mark-sweep 1403.5 (1469.2) -> 1403.5 (1469.2) MB, 3311.7 / 0.0 ms  last resort


<--- JS stacktrace --->

==== JS stack trace =========================================

Security context: 000002E66029CEA9 <JSObject>
    1: getTypeReferenceId(aka getTypeReferenceId) [C:\nodejs\node_modules\typescript\lib\tsc.js:~26377] [pc=0000014DCA819BD0](this=
000002E660282241 <undefined>,type=000002FC83FFBC51 <Type map = 0000008AEC429EF9>,typeParameters=00000388F03E8951 <JSArray[1]>,depth
=000002E660282241 <undefined>)
    2: arguments adaptor frame: 2->3
    3: getRelationKey(aka getRelationKey) [C:\nodejs\node_modules\...

FATAL ERROR: CALL_AND_RETRY_LAST Allocation failed - JavaScript heap out of memory
The terminal process terminated with exit code: 3

Terminal will be reused by tasks, press any key to close it.

[mhegazy]

The stack trace is inconsequential here. the process runs out of memory, it does not really matter where it crashes, what matters is why is it filling up memory.

[pocesar]

Files:           121
Lines:         64003
Nodes:        261277
Identifiers:   88809
Symbols:      136598
Types:         34024
Memory used: 146529K
I/O read:      0.85s
I/O write:     0.04s
Parse time:    2.95s
Bind time:     1.58s
Check time:    5.19s
Emit time:     1.21s
Total time:   10.92s
14:09:01 - Compilation complete. Watching for file changes.

it will crash again in a couple of minutes, I'll see if anything changes

[mhegazy]

so it does not crash without --watch?

[pocesar]

so far I've been able to build without watch, but when using -w it randomly crashes after a couple of compilations

14:24:33 - File change detected. Starting incremental compilation...


Files:           121
Lines:         64003
Nodes:        261277
Identifiers:   88809
Symbols:      136598
Types:         34024
Memory used: 197127K
I/O read:      0.01s
I/O write:     0.01s
Parse time:    1.15s
Bind time:     0.02s
Check time:    5.19s
Emit time:     0.95s
Total time:    7.31s
14:24:41 - Compilation complete. Watching for file changes.


14:42:00 - File change detected. Starting incremental compilation...


Files:           121
Lines:         64004
Nodes:        261277
Identifiers:   88809
Symbols:      136598
Types:         34024
Memory used: 242675K
I/O read:      0.00s
I/O write:     0.02s
Parse time:    0.60s
Bind time:     0.02s
Check time:    4.27s
Emit time:     0.74s
Total time:    5.62s
14:42:05 - Compilation complete. Watching for file changes.

the memory is ever increasing though

[mhegazy]

aah.. that indicates there is a memory leak for --watch. do you see this with other projects?

[pocesar]

yes, it usually reaches a point where my machine slows to a crawl, and even vscode crashes (because I have 5 editors opened, all with TSC with watch, using nightly for all of them, even for vscode)

Files:           121
Lines:         64004
Nodes:        261277
Identifiers:   88809
Symbols:      136598
Types:         34024
Memory used: 329374K
I/O read:      0.00s
I/O write:     0.00s
Parse time:    0.84s
Bind time:     0.02s
Check time:    3.48s
Emit time:     0.61s
Total time:    4.95s
15:25:30 - Compilation complete. Watching for file changes.

[taoqf]

try this:
node --max-old-space-size=4096 ./node_modules/.bin/tsc
may work for you.