Comparing version 0.2.2 to 0.2.3
{ | ||
"name": "heapdump", | ||
"main": "./build/Release/heapdump", | ||
"version": "0.2.2", | ||
"version": "0.2.3", | ||
"description": "Make a dump of the V8 heap for later inspection.", | ||
@@ -6,0 +6,0 @@ "homepage": "https://github.com/bnoordhuis/node-heapdump", |
@@ -41,2 +41,7 @@ node-heapdump | ||
The SIGUSR2 signal handler is enabled by default but you can disable it | ||
by setting `NODE_HEAPDUMP_OPTIONS=nosignal` in the environment: | ||
$ env NODE_HEAPDUMP_OPTIONS=nosignal node script.js | ||
### Inspecting the snapshot | ||
@@ -55,1 +60,10 @@ | ||
extension. | ||
### Caveats | ||
On UNIX systems, the rule of thumb for creating a heap snapshot is that it | ||
requires memory twice the size of the heap at the time of the snapshot. | ||
If you end up with empty or truncated snapshot files, check the output of | ||
`dmesg`; you may have had a run-in with the system's OOM killer or a resource | ||
limit enforcing policy, like `ulimit -u` (max user processes) or `ulimit -v` | ||
(max virtual memory size). |
Sorry, the diff of this file is not supported yet
License Policy Violation
LicenseThis package is not allowed per your license policy. Review the package's license to ensure compliance.
Found 1 instance in 1 package
License Policy Violation
LicenseThis package is not allowed per your license policy. Review the package's license to ensure compliance.
Found 1 instance in 1 package
12698
68
10