You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Version: output of node -v
Platform: output of uname -a (UNIX), or version and 32 or 64-bit (Windows)
Subsystem: if known, please specify affected core module name
-->
Attempt to work-around issue by setting report file name to /dev/null :
node --experimental-report --report-on-fatalerror --report-filename=/dev/null /var/www/html2/test.js
FATAL ERROR: CALL_AND_RETRY_LAST Allocation failed - JavaScript heap out of memory
Writing Node.js report to file: report.20200221.165821.14530.0.001.json
Node.js report completed
Aborted
CalebCarroll
changed the title
experimental-report feature enabled as default setting in 12.16.1 LTS
experimental-report enabled by default and report files created regardless of command line parameters
Feb 21, 2020
CalebCarroll
changed the title
experimental-report enabled by default and report files created regardless of command line parameters
All versions from 12.0.0 through 13.9.0: experimental-report enabled by default and report files created regardless of command line parameters.
Feb 21, 2020
Version: output of
node -v
Platform: output of
uname -a
(UNIX), or version and 32 or 64-bit (Windows)Subsystem: if known, please specify affected core module name
-->
What steps will reproduce the bug?
Cause out of memory condition
How often does it reproduce? Is there a required condition?
100%
What is the expected behavior?
node should not create any report files
What do you see instead?
node creates a report file regardless of any command line settings
Additional information
No command line options:
node /var/www/html2/test.js
FATAL ERROR: CALL_AND_RETRY_LAST Allocation failed - JavaScript heap out of memory
Writing Node.js report to file: report.20200221.165442.10713.0.001.json
Node.js report completed
Aborted
"header": {
"reportVersion": 1,
"event": "Allocation failed - JavaScript heap out of memory",
"trigger": "FatalError",
"filename": "report.20200221.165442.10713.0.001.json",
"dumpEventTime": "2020-02-21T16:54:42Z",
"dumpEventTimeStamp": "1582304082557",
"processId": 10713,
"cwd": "/var/active/html2",
"commandLine": [
"node",
"/var/www/html2/test.js"
],
"nodejsVersion": "v12.16.1",
"glibcVersionRuntime": "2.28",
"glibcVersionCompiler": "2.24",
"wordSize": 32,
"arch": "arm",
"platform": "linux",
"componentVersions": {
"node": "12.16.1",
"v8": "7.8.279.23-node.31",
"uv": "1.34.0",
"zlib": "1.2.11",
"brotli": "1.0.7",
"ares": "1.15.0",
"modules": "72",
"nghttp2": "1.40.0",
"napi": "5",
"llhttp": "2.0.4",
"http_parser": "2.9.3",
"openssl": "1.1.1d",
"cldr": "35.1",
"icu": "64.2",
"tz": "2019c",
"unicode": "12.1"
},
"release": {
"name": "node",
"lts": "Erbium",
"headersUrl": "https://nodejs.org/download/release/v12.16.1/node-v12.16.1-headers.tar.gz",
"sourceUrl": "https://nodejs.org/download/release/v12.16.1/node-v12.16.1.tar.gz"
},
"osName": "Linux",
"osRelease": "4.19.50-v7+",
"osVersion": "#896 SMP Thu Jun 20 16:11:44 BST 2019",
"osMachine": "armv7l",
.
.
.
Attempt to work-around issue by setting report file name to /dev/null :
node --experimental-report --report-on-fatalerror --report-filename=/dev/null /var/www/html2/test.js
FATAL ERROR: CALL_AND_RETRY_LAST Allocation failed - JavaScript heap out of memory
Writing Node.js report to file: report.20200221.165821.14530.0.001.json
Node.js report completed
Aborted
"header": {
"reportVersion": 1,
"event": "Allocation failed - JavaScript heap out of memory",
"trigger": "FatalError",
"filename": "report.20200221.165821.14530.0.001.json",
"dumpEventTime": "2020-02-21T16:58:21Z",
"dumpEventTimeStamp": "1582304301387",
"processId": 14530,
"cwd": "/var/active/html2",
"commandLine": [
"node",
"--experimental-report",
"--report-on-fatalerror",
"--report-filename=/dev/null",
"/var/www/html2/test.js"
],
The text was updated successfully, but these errors were encountered: