Tag Archives: out of memory

[azure application service] the application deployed under the app service reports an error out of memory

Problem description

After the app is deployed to the app service, an out of memory error is encountered.

 

Error message: GetData   Error:, Exception of type ‘System.OutOfMemoryException’ was thrown.,

at System.IO.MemoryStream.set_ Capacity(Int32 value)

at System.IO.MemoryStream.EnsureCapacity(Int32 value)

at System.IO.MemoryStream.Write(Byte[] buffer, Int32 offset, Int32 count)

at OfficeOpenXml.Packaging.ZipPackage..ctor(Stream stream)

at OfficeOpenXml.ExcelPackage.ConstructNewFile(String password)

at OfficeOpenXml.ExcelPackage..ctor(FileInfo newFile)

at MyLife.Utility.ExcelHelper.LoadDataTableFromFile(String fileName)

at MyLife.Serivces.GetData()

 

2021-09-12 05:19:57.0362 | Error | HCPService-StartPreprocessing-Exception of type ‘System.OutOfMemoryException’ was thrown.-

2021-09-12 05:19:57.0756 | Error | An unhandled exception has occurred while executing the request. System.OutOfMemoryException: Exception of type ‘System.OutOfMemoryException’ was thrown.

Problem solving

In the case of oom error at the beginning of deployment, it means that the memroy of the current pricing layer is not enough to meet the operation of the application. However, the memory of different pricing layers of APP service is different. The lowest free layer has 1g ram and the highest can reach 14g.

  （Source ：   https://www.azure.cn/pricing/details/app-service/ ）  

 

If the memory limitation of the pricing layer is excluded, another important factor is the platform setting of APP service.

App service supports 32-bit and 64 bit platform systems. Therefore, if the default setting is 32-bit operating system, it only supports 4G memory at most. In order to make the application use the maximum memory and not waste the ram resources of APP service, when facing the problem of oom, modify the 64 bit platform bit of APP service at the first time. If oom still occurs, you can consider upgrading the pricing layer of APP service.

 

[END]

 

NPM Command Error: Allocation failed – JavaScript heap out of memory

Error occurred when executing NPM command:

FATAL ERROR: Ineffective mark-compacts near heap limit Allocation failed – JavaScript heap out of memory

The reason is that there is not enough memory in JavaScript heap. Node is based on V8 engine. When using memory through JavaScript in node, only part of memory can be used (about 1.4 GB in 64 bit system). If memory is not enough, you can use the following methods to relax the default memory limit of V8.

Method 1:

add parameters  — max_ old_ space_ size=4096

npm run start --max_ old_ space_ size=4096

Method 2:

modify the CMD file

In the directory node_ Open ng.cmd and ngc.cmd files under modules /. Bin, and add  — max_ old_ space_ size=4096

Method 3:

through the increase memory limit plug-in

Install plug-in: NPM install – G increase memory limit

Execute command: NPX cross env limit = 4096 increase memory limit

Through the log, we can find that it will add the — Max old space size = 4096 parameter to all the places where the node command is executed