[BUG] Memory error during main graph generation

Overview of the issue

An error is thrown while generating the main graph:

[08:40:15] Process main graph
Cannot enlarge memory arrays. Either (1) compile with  -s TOTAL_MEMORY=X  with X higher than the current value 16777216, (2) compile with  -s ALLOW_MEMORY_GROWTH=1  which adjusts the size at runtime but prevents some optimizations, (3) set Module.TOTAL_MEMORY to a higher value before the program runs, or if you want malloc to return NULL (0) instead of this abort, compile with  -s ABORTING_MALLOC=0
Cannot enlarge memory arrays. Either (1) compile with  -s TOTAL_MEMORY=X  with X higher than the current value 16777216, (2) compile with  -s ALLOW_MEMORY_GROWTH=1  which adjusts the size at runtime but prevents some optimizations, (3) set Module.TOTAL_MEMORY to a higher value before the program runs, or if you want malloc to return NULL (0) instead of this abort, compile with  -s ABORTING_MALLOC=0
[08:40:16] Ooops error during main graph generation, moving on next part with main graph disabled : : abort("Cannot enlarge memory arrays. Either (1) compile with  -s TOTAL_MEMORY=X  with X higher than
the current value 16777216, (2) compile with  -s ALLOW_MEMORY_GROWTH=1  which adjusts the size at runtime but prevents some optimizations, (3) set Module.TOTAL_MEMORY to a higher value before the program runs, or if you want malloc to return NULL (0) instead of this abort, compile with  -s ABORTING_MALLOC=0 ") at Error
    at jsStackTrace (C:\Development\Web UI\Main\Test.App\node_modules\viz.js\viz.js:27:15589)
    at stackTrace (C:\Development\Web UI\Main\Test.App\node_modules\viz.js\viz.js:27:15760)
    at abort (C:\Development\Web UI\Main\Test.App\node_modules\viz.js\viz.js:50:6350)
    at abortOnCannotGrowMemory (C:\Development\Web UI\Main\Test.App\node_modules\viz.js\viz.js:27:16630)
    at enlargeMemory (C:\Development\Web UI\Main\Test.App\node_modules\viz.js\viz.js:27:17075)
    at H6 (C:\Development\Web UI\Main\Test.App\node_modules\viz.js\viz.js:43:12336)
    at k6 (C:\Development\Web UI\Main\Test.App\node_modules\viz.js\viz.js:42:105869)
    at IK (C:\Development\Web UI\Main\Test.App\node_modules\viz.js\viz.js:35:82215)
    at HK (C:\Development\Web UI\Main\Test.App\node_modules\viz.js\viz.js:35:82147)
    at mV (C:\Development\Web UI\Main\Test.App\node_modules\viz.js\viz.js:36:137849)
If this abort() is unexpected, build with -s ASSERTIONS=1 which can give more information.

Operating System, Node.js, npm, compodoc version(s)

OS: Windows 10x64 RAM: 16GB Node: 6.11.3 NPM: 3.10.10

Angular configuration, a package.json file in the root folder

package.json:

...
"dependencies": {
    "@angular/animations": "~5.1.1",
    "@angular/cdk": "5.0.1",
    "@angular/common": "~5.1.1",
    "@angular/compiler": "~5.1.1",
    "@angular/core": "~5.1.1",
    "@angular/flex-layout": "~2.0.0-beta.12",
    "@angular/forms": "~5.1.1",
    "@angular/http": "~5.1.1",
    "@angular/material": "5.0.1",
    "@angular/platform-browser": "~5.1.1",
    "@angular/platform-browser-dynamic": "~5.1.1",
    "@angular/router": "~5.1.1",
    "classlist.js": "^1.1.20150312",
    "core-js": "~2.5.3",
    "date-fns": "^1.29.0",
    "fuse.js": "^3.2.0",
    "hammerjs": "^2.0.8",
    "lodash": "~4.17.4",
    "object-hash": "~1.2.0",
    "quagga": "^0.12.1",
    "quirc-js": "^1.1.2",
    "rxjs": "~5.5.5",
    "web-animations-js": "^2.3.1",
    "zone.js": "~0.8.18"
  },
  "devDependencies": {
    "@angular/cli": "~1.6.1",
    "@angular/compiler-cli": "~5.1.1",
    "@angular/language-service": "~5.1.1",
    "@compodoc/compodoc": "~1.0.5",
    "@types/chance": "~0.7.35",
    "@types/fuse": "~2.5.2",
    "@types/jasmine": "~2.8.2",
    "@types/jasminewd2": "~2.0.3",
    "@types/lodash": "~4.14.91",
    "@types/node": "~8.5.1",
    "@types/object-hash": "~1.1.0",
    "@types/tinycolor2": "~1.4.0",
    "ajv": "^5.5.2",
    "chance": "~1.0.12",
    "codelyzer": "~4.0.2",
    "cpx": "~1.5.0",
    "cross-env": "~5.1.1",
    "jasmine-core": "~2.8.0",
    "jasmine-spec-reporter": "~4.2.1",
    "karma": "~1.7.1",
    "karma-chrome-launcher": "~2.2.0",
    "karma-cli": "~1.0.1",
    "karma-coverage-istanbul-reporter": "~1.3.0",
    "karma-html-reporter": "^0.2.7",
    "karma-jasmine": "~1.1.1",
    "karma-jasmine-html-reporter": "~0.2.2",
    "karma-junit-reporter": "^2.0.0",
    "karma-spec-reporter": "~0.0.32",
    "karma-tfs-reporter": "^1.0.1",
    "ngx-i18nsupport": "~0.9.0",
    "npm-run-all": "~4.1.2",
    "protractor": "~5.2.2",
    "replace": "^0.3.0",
    "replace-in-file": "^3.0.0",
    "rimraf": "~2.6.2",
    "rxjs-tslint-rules": "^3.3.0",
    "tinycolor2": "~1.4.1",
    "ts-node": "~4.0.2",
    "tslint": "~5.8.0",
    "typescript": "2.4.2"
  }

Compodoc installed globally or locally ?

Locally

[javafrog]

This problem is still unsolved, there are only workarounds (i.e., disabling graph generation altogether). Would be glad if there was a fix!

[timwright35]

@vogloblinsky Thanks for the information, I managed to get it to work, minus the main app graph generation, with node --max_old_space_size=8192 (path to node)/node_modules/@compodoc/compodoc/bin/index-cli.js