web-dev-qa-db-fra.com

Mark-compacts inefficaces près de la limite de tas Allocation Angular 8 - Tas de JavaScript hors de la mémoire

42% construisant 274/275 modules 1 actifs ...\src\index.js ?? extraits! D:\Clients\community.web.v2\node_modules\sass-loader\lib\loader.js ?? ref - 15 -3! D:\Clients\Nalaka\dc2vue.community.web.v2\src\styles.scss <--- Derniers GCs --->

[12996: 000002DFC57D42F0] 43111 ms: récupération 1335,4 (1425,0) -> 1335,3 (1426,0) Mo, 2,6/0,0 ms (mu moyen = 0,169, mu actuel = 0,100) échec d'allocation [12996: 000002DFC57D42F0] 43489 ms: balayage 1336,2 (1426,0) -> 1335,4 (1425,5) Mo, 375,8/0,0 ms (mu moyen = 0,144, mu actuel = 0,100) le nettoyage d'échec d'allocation peut échouer

<--- JS stacktrace --->

==== Trace de pile JS ==========================================

0: ExitFrame [pc: 00000257D3FDC5C1] Security context: 0x00b77541e6e9 <JSObject>
1: createNode [000001A31ED4EFF1] [D:\Clients\community.web.v2\node_modules\TypeScript\lib\TypeScript.js:~16489]

[pc = 00000257D55AD889] (this = 0x02b823cedf89, kind = 275, pos = - = - 1, end = -1) 2: createPropertyAssignment [000001A31ED54669] [D:\Clients\community.web.v2\node_modules\TypeScript\lib\typescri ...

ERREUR FATALE: Échec de l'allocation des marqueurs compacts près de la limite de tas - Tas de mémoire JavaScript insuffisant 1: 00007FF76C26DD8A v8 :: internal :: GCIdleTimeHandler :: GCIdleTimeHandler + 4506 2: 00007FF76C248886 node :: MakeCallback + 4534 3: 00007FF76C249200reg 00007FF76C5630DE v8 :: interne :: FatalProcessOutOfMemory + 846 5: 00007FF76C56300F v8 :: interne :: FatalProcessOutOfMemory + 639 6: 00007FF76C749804 v8 :: interne :: Tas :: Opérateur MaxHeapGrowingFactor + 9620 7: 00007FF76C7J = + 24550 8: 00007FF76C73EE3C v8 :: interne :: ScavengeJob :: operator = + 17980 9: 00007FF76C747B87 v8 :: internal :: Heap :: MaxHeapGrowingFactor + 2327 10: 00007FF76C747C06 v8 :: internal :: Heap :: MaxHeapGrowingFactor + 2454 11 : 00007FF76C871EA7 v8 :: interne :: Usine :: NewFillerObject + 55 12: 00007FF76C8EF096 v8 :: interne :: opérateur << + 73494 13: 00000257D3FDC5C1

J'ai essayé cette solution: https://github.com/angular/angular-cli/issues/5618#issuecomment-450151214

c'est à dire.

package.json

"scripts": {
        "ng": "ng",
        "ng-high-memory": "node --max_old_space_size=8000 ./node_modules/@angular/cli/bin/ng",// here
        "start": "ng serve",
        "build:prod": "ng build --configuration=prod",
    },

Après ça

npm exécuter ng-high-memory --build --prod

Mais ça dit

> > [email protected] ng-high-memory D:\Clients\community.web.v2
> > node --max_old_space_size=8000 ./node_modules/@angular/cli/bin/ng
> 
> Available Commands:   add Adds support for an external library to your
> project.   analytics Configures the gathering of Angular CLI usage
> metrics. See https://v8.angular.io/cli/usage-analytics-gathering.  
> build (b) Compiles an Angular app into an output directory named dist/
> at the given output path. Must be executed from within a workspace
> directory.   deploy (d) Invokes the deploy builder for a specified
> project or for the default project in the workspace.   config
> Retrieves or sets Angular configuration values in the angular.json
> file for the workspace.   doc (d) Opens the official Angular
> documentation (angular.io) in a browser, and searches for a given
> keyword.   e2e (e) Builds and serves an Angular app, then runs
> end-to-end tests using Protractor.   generate (g) Generates and/or
> modifies files based on a schematic.   help Lists available commands
> and their short descriptions.   lint (l) Runs linting tools on Angular
> app code in a given project folder.   new (n) Creates a new workspace
> and an initial Angular app.   run Runs an Architect target with an
> optional custom builder configuration defined in your project.   serve
> (s) Builds and serves your app, rebuilding on file changes.   test (t)
> Runs unit tests in a project.   update Updates your application and
> its dependencies. See https://update.angular.io/   version (v) Outputs
> Angular CLI version.   xi18n Extracts i18n messages from source code.
> 
> For more detailed help run "ng [command name] --help"

Alors, comment puis-je exécuter cette commande correctement?

Remarque: J'utilise la dernière Angular i.e. "@angular/core": "^8.2.14", et "@angular/cli": "^8.3.19",

node.jsangulartypescript
3
Sampath

Sur mon modèle Raspberry Pi 3, l'espace RAM (1 Go) et swap (1 Go) était trop petit. Après avoir augmenté l'espace swap à 10 Go, la commande suggérée "ng-high-memory" a fonctionné !

0
Rob Lassche