Closed codehippie1 closed 5 years ago
I do not know why but I got this error last week. I fixed our automated build by updating the webpack script as follows (I put a random higher number).
"build:webpack": "webpack --max_old_space_size=16384 --progress --color",
However, later I read that apparently, the correct approach is to set an environment variable
NODE_OPTIONS=--max_old_space_size=16384
Hope it helps.
@alexbenitez I have tried
"build:webpack": "webpack --max_old_space_size=16384 --progress --color",
and it didnt work.
How to set the environment variable for Azure DevOps build agents? Where does the line of code you show go, file, location etc?
@alexbenitez I just added a Azure powershell task to pipeline, just before build to set environment variable at machine level. It didn't work either.
See YAML below
steps:
- task: AzurePowerShell@3
displayName: 'Azure PowerShell script: InlineScript'
inputs:
azureSubscription: 'NYCSCA Azure Dev/Test (ea91a274-55c6-461c-a11d-758ef02c2698)'
ScriptType: InlineScript
Inline: '[Environment]::SetEnvironmentVariable("NODE_OPTIONS", "--max_old_space_size=4096", "Machine")'
FailOnStandardError: true
azurePowerShellVersion: LatestVersion
Update: Anyone trying this on Azure build pipeline. I finally got it succeeded. Increased memory to 16384. Please note this step alone wasn't working. Needed same changes in csproj and package.json
Steps
Azure build pipeline task
-> Azure powershell script:Inlinescript
before Compile with below settings
steps:
- task: AzurePowerShell@3
displayName: 'Azure PowerShell script: InlineScript'
inputs:
azureSubscription: 'NYCSCA Azure Dev/Test (ea91a274-55c6-461c-a11d-758ef02c2698)'
ScriptType: InlineScript
Inline: '[Environment]::SetEnvironmentVariable("NODE_OPTIONS", "--max_old_space_size=16384", "Machine")'
FailOnStandardError: true
azurePowerShellVersion: LatestVersion
@alexbenitez thanks for the tip NODE_OPTIONS=--max_old_space_size=16384
. It worked perfectly.
Update: Anyone trying this on Azure build pipeline. I finally got it succeeded. Increased memory to 16384. Please note this step alone wasn't working. Needed same changes in csproj and package.json
Steps
- Add an
Azure build pipeline task
->Azure powershell script:Inlinescript
before Compile with below settings steps:- task: AzurePowerShell@3 displayName: 'Azure PowerShell script: InlineScript' inputs: azureSubscription: 'NYCSCA Azure Dev/Test (ea91a274-55c6-461c-a11d-758ef02c2698)' ScriptType: InlineScript Inline: '[Environment]::SetEnvironmentVariable("NODE_OPTIONS", "--max_old_space_size=16384", "Machine")' FailOnStandardError: true azurePowerShellVersion: LatestVersion
@codehippie1 what changes are required for csproj and package.json files?
Solution for Azure Pipeline in Azure DevOps:
- task: PowerShell@2
displayName: Build
env:
NODE_OPTIONS: --max_old_space_size=16384
Set the Environment VariableNODE_OPTIONS
with value --max_old_space_size=16384
in your Build-Task.
Solución para Azure Pipeline en Azure DevOps:
- task: PowerShell@2 displayName: Build env: NODE_OPTIONS: --max_old_space_size=16384
Establezca la Variable de entorno
NODE_OPTIONS
con valor--max_old_space_size=16384
en su Tarea de compilación.
No funciona, debo tener esta varible en el package
I got this error when trying to run it
2023-08-05T07:55:39.1552140Z ##[section]Starting: PowerShell Script 2023-08-05T07:55:39.1998002Z ============================================================================== 2023-08-05T07:55:39.1998347Z Task : PowerShell 2023-08-05T07:55:39.1998582Z Description : Run a PowerShell script on Linux, macOS, or Windows 2023-08-05T07:55:39.1998804Z Version : 2.220.0 2023-08-05T07:55:39.1999026Z Author : Microsoft Corporation 2023-08-05T07:55:39.1999310Z Help : https://docs.microsoft.com/azure/devops/pipelines/tasks/utility/powershell 2023-08-05T07:55:39.1999663Z ============================================================================== 2023-08-05T07:55:41.2025679Z Generating script. 2023-08-05T07:55:41.2852176Z ========================== Starting Command Output =========================== 2023-08-05T07:55:41.3104082Z ##[command]"C:\Windows\System32\WindowsPowerShell\v1.0\powershell.exe" -NoLogo -NoProfile -NonInteractive -ExecutionPolicy Unrestricted -Command ". 'F:\Ag2_work_temp\73e90371-e9d8-4834-b4bf-6d8c9cf3f029.ps1'" 2023-08-05T07:55:42.0673357Z ##[error]Exception calling "SetEnvironmentVariable" with "3" argument(s): "Requested registry access is not allowed." At F:\Ag2_work_temp\73e90371-e9d8-4834-b4bf-6d8c9cf3f029.ps1:4 char:1
+ CategoryInfo : NotSpecified: (:) [], ParentContainsErrorRecordException
+ FullyQualifiedErrorId : SecurityException
2023-08-05T07:55:42.1487257Z ##[error]PowerShell exited with code '1'.
2023-08-05T07:55:42.1767622Z ##[section]Finishing: PowerShell Script
The strange thing is that no one changed the pipeline, as well running old build that were succeding bring the javascript error
Getting "Ineffective mark-compacts near heap limit Allocation failed - JavaScript heap out of memory" on all azure builds. Local builds are fine.
PS: I have seen Issue# 262
What did I try?
RunWebpack
to addnode --max_old_space_size=4096
. I see this gets executed twice andmax_old_space_size
is being ignored the second time. See below error.Exact Error:
Location of Error: