Intel® Collaboration Suite for WebRTC
Community support and discussions on the Intel® Collaboration Suite for WebRTC (Intel® CS for WebRTC).
Announcements
Welcome to the Intel Community. If you get an answer you like, please mark it as an Accepted Solution to help others. Thank you!
For the latest information on Intel’s response to the Log4j/Log4Shell vulnerability, please see Intel-SA-00646

Memory Leak Error

Naresh_R_1
New Contributor I
149 Views

Dear Team,

I found the below error when my mcu crashed, please let me know what could be the reason'

2019-08-28 05:45:47.031  - INFO: NodeManager - Node webrtc-c167bb2896fe2cf8a4bb@172.31.14.68_43 is closed on unexpected code: null

2019-08-28 10:42:34.936  - INFO: NodeManager - Node webrtc-c167bb2896fe2cf8a4bb@172.31.14.68_107 is closed on unexpected code: null

2019-08-29 10:34:11.481  - INFO: NodeManager - Node webrtc-c167bb2896fe2cf8a4bb@172.31.14.68_190 is closed on unexpected code: null

2019-09-03 07:24:01.439  - INFO: NodeManager - Node webrtc-c167bb2896fe2cf8a4bb@172.31.14.68_355 is closed on unexpected code: null

2019-09-03 09:13:24.622  - INFO: NodeManager - Node webrtc-c167bb2896fe2cf8a4bb@172.31.14.68_370 is closed on unexpected code: null

2019-09-03 09:36:39.087  - INFO: NodeManager - Node webrtc-c167bb2896fe2cf8a4bb@172.31.14.68_381 is closed on unexpected code: null

2019-09-03 11:59:55.262  - INFO: NodeManager - Node webrtc-c167bb2896fe2cf8a4bb@172.31.14.68_410 is closed on unexpected code: null

2019-09-08 13:37:10.257  - INFO: LoadCollector - To stop load collector.

internal/child_process.js:313

    throw errnoException(err, 'spawn');

    ^

 

Error: spawn ENOMEM

    at ChildProcess.spawn (internal/child_process.js:313:11)

    at exports.spawn (child_process.js:508:9)

    at Object.exports.execFile (child_process.js:218:15)

    at Object.exports.exec (child_process.js:148:18)

    at Timeout.<anonymous> (/home/centos/Release-v4.2/webrtc_agent/loadCollector.js:1:1222)

    at ontimeout (timers.js:498:11)

    at tryOnTimeout (timers.js:323:5)

    at Timer.listOnTimeout (timers.js:290:5)

[root@ip-172-31-14-68 logs]# cat webrtc-c167bb2896fe2cf8a4bb@172.31.14.68_648.log

 

Thanks

Naresh

0 Kudos
1 Reply
Li_C_Intel
Employee
149 Views

Have you checked which process consumed too much memory? E.g. using 'top command.

Reply