node-oom-heapdump 3.5.0 → 3.6.0
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/CHANGELOG.md +3 -3
- package/README.md +10 -0
- package/package.json +7 -7
package/CHANGELOG.md
CHANGED
package/README.md
CHANGED
|
@@ -12,6 +12,16 @@ Also comes with prebuilt binaries (hosted on Github releases), thanks to Stuart
|
|
|
12
12
|
From 3.1.0, prebuilt binaries are only shipped for Node.js 16.x and upwards.
|
|
13
13
|
From 3.2.3, prebuilt binaries are only shipped for Node.js 18.x and upwards.
|
|
14
14
|
|
|
15
|
+
## Node 22.x
|
|
16
|
+
Since node 22.x, there is a new CLI flag for generating heapdumps. This one is supplied by V8 (not Node.js) and is more reliant and efficient in creating the heapdumps than Node.js' `--heapsnapshot-near-heap-limit`.
|
|
17
|
+
More information: https://github.com/nodejs/node/issues/50711#issuecomment-2149559816
|
|
18
|
+
|
|
19
|
+
```
|
|
20
|
+
node --heap-snapshot-on-oom index.js
|
|
21
|
+
```
|
|
22
|
+
Since node 22.x we had issues with no heapdumps being created in production sometimes (via `--heapsnapshot-near-heap-limit`), which did work when using V8's `--heap-snapshot-on-oom`.
|
|
23
|
+
The only disadvantage i encountered is that the filename of the heapdump file does not include a process ID, just the timestamp.
|
|
24
|
+
|
|
15
25
|
## Node.js 14.18.x
|
|
16
26
|
https://github.com/nodejs/node/pull/33010 landed in Node.js 14.18.0, which makes this module no longer needed for heapdumps on out of memory.
|
|
17
27
|
One can use the `--heapsnapshot-near-heap-limit` Node.js CLI option as an alternative.
|
package/package.json
CHANGED
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
{
|
|
2
2
|
"name": "node-oom-heapdump",
|
|
3
|
-
"version": "3.
|
|
3
|
+
"version": "3.6.0",
|
|
4
4
|
"description": "Create a V8 heap snapshot when an \"Out of Memory\" error occurs, or create a heap snapshot or CPU profile on request.",
|
|
5
5
|
"main": "index.js",
|
|
6
6
|
"scripts": {
|
|
@@ -38,14 +38,14 @@
|
|
|
38
38
|
},
|
|
39
39
|
"homepage": "https://github.com/blueconic/node-oom-heapdump#readme",
|
|
40
40
|
"devDependencies": {
|
|
41
|
-
"
|
|
42
|
-
"bindings": "^1.5.0",
|
|
43
|
-
"eslint-config-google": "^0.14.0",
|
|
44
|
-
"nan": "^2.22.0"
|
|
41
|
+
"eslint-config-google": "^0.14.0"
|
|
45
42
|
},
|
|
46
43
|
"dependencies": {
|
|
47
|
-
"
|
|
44
|
+
"@mapbox/node-pre-gyp": "2.0.0",
|
|
45
|
+
"bindings": "^1.5.0",
|
|
46
|
+
"chrome-remote-interface": "^0.33.3",
|
|
47
|
+
"nan": "^2.22.2",
|
|
48
48
|
"require-main-filename": "^2.0.0",
|
|
49
|
-
"ws": "^8.18.
|
|
49
|
+
"ws": "^8.18.2"
|
|
50
50
|
}
|
|
51
51
|
}
|