# v8-profiler-node8

> based on v8-profiler@5.7.0, solved the v8-profiler segment fault error in node 8.x+

Latest version **6.4.0** (published 2022-05-27) · BSD-2-Clause license · 0 weekly downloads

## Install

```sh
npm install v8-profiler-node8
pnpm add v8-profiler-node8
yarn add v8-profiler-node8
bun add v8-profiler-node8
```

## Health

**Score 15/100 (F)** — status: abandoned.

Positive: no vulnerabilities.

Warnings: low downloads; no types; no esm support.

Negative: abandoned; low maintenance score.

## Facts

| | |
|---|---|
| Version | 6.4.0 |
| Published | 2022-05-27 |
| First published | 2017-06-16 |
| Weekly downloads | 0 |
| License | BSD-2-Clause |
| TypeScript types | none |
| Module format | CommonJS |
| Node | >=0.10 |
| Dependencies | 1 |
| Unpacked size | 8.4 KB |
| Known vulnerabilities | 0 |
| Install scripts | no |
| GitHub stars | 55 |
| Author | hyj1991 |
| Maintainers | widdershin, hyj1991 |
| Keywords | profiler, inspector |

## Links

- npm: https://www.npmjs.com/package/v8-profiler-node8
- Repository: https://github.com/hyj1991/v8-profiler-node8
- Homepage: http://github.com/hyj1991/v8-profiler-node8
- Issues: https://github.com/hyj1991/v8-profiler-node8/issues
- npm.io page: https://npm.io/package/v8-profiler-node8

## Dependencies (1)

- [v8-profiler-next](https://npm.io/package/v8-profiler-next.md) ^1.7.1

## Recent versions

- 6.4.0 (latest) — 2022-05-27
- 7.4.0 (next) — 2022-06-18
- 7.3.0 — 2021-09-06
- 7.2.1 — 2021-06-29
- 7.1.1 — 2020-08-19
- 7.1.0 — 2020-07-09
- 6.3.0 — 2020-06-17
- 6.2.0 — 2020-05-04
- 6.1.1 — 2019-07-10
- 6.1.0 — 2019-07-01
- 7.0.1 — 2019-07-01
- 7.0.0 — 2019-06-23
- 6.0.1 — 2018-08-28
- 6.0.0 — 2018-06-13
- 5.7.8 — 2018-05-11
- … 5 more at https://npm.io/package/v8-profiler-node8/versions

## README

[![npm version](https://img.shields.io/npm/v/v8-profiler-node8/latest.svg)](https://www.npmjs.com/package/v8-profiler-node8)
[![Continuous integration](https://github.com/hyj1991/v8-profiler-node8/actions/workflows/nodejs.yml/badge.svg?branch=master)](https://github.com/hyj1991/v8-profiler-node8/actions/workflows/nodejs.yml?query=branch:master)
[![downloads info](https://img.shields.io/npm/dm/v8-profiler-node8.svg)](https://www.npmjs.com/package/v8-profiler-node8)
[![license](https://img.shields.io/npm/l/v8-profiler-node8.svg)](LICENSE)

# Description
Based on v8-profiler-node8@5.7.0, Solved the v8-profiler segment fault error in node-v8.x+.

v8-profiler-node8 provides [node](http://github.com/nodejs/node) bindings for the v8
profiler and integration with [node-inspector](http://github.com/node-inspector)

# Compatibility
* **Platform**
  * mac (x64 / arm64)
  * linux (x64 / arm64)
  * windows (x64)

* **Node version**
  * v4.x
  * v5.x
  * v6.x
  * v7.x
  * v8.x
  * v9.x
  * v10.x
  * v11.x
  * v12.x
  * v13.x
  * v14.x
  * v15.x
  * v16.x
  * v17.x
  * v18.x

## Installation
```sh
npm install v8-profiler-node8
```
## Usage
```js
var profiler = require('v8-profiler-node8');
```
## API
`takeSnapshot([name])` - returns new HEAP Snapshot instance. `name` is optional argument, by default snapshot name will be constructed from his uid.

`deleteAllSnapshots()` - works as described in name.

```js
const profiler = require('v8-profiler-node8')
var snapshot1 = profiler.takeSnapshot('1');
var snapshot2 = profiler.takeSnapshot()
console.log(profiler.snapshots);
profiler.deleteAllSnapshots();
```

`startProfiling([name], [recsamples])` - start CPU profiling. `name` is optional argument, by default profile name will be constructed from his uid. `recsamples` is true by default.

`stopProfiling([name])` - returns new CPU Profile instance. There is no strictly described behavior for usage without `name` argument.

`setSamplingInterval([num])` - Changes default CPU profiler sampling interval to the specified number of microseconds. Default interval is 1000us. This method must be called when there are no profiles being recorded. If called without arguments it resets interval to default.

`deleteAllProfiles()` - works as described in name.

`collectSample()` - causes all active profiles to synchronously record the current callstack. Does not add a new top level sample, only adds more detail to the call graph.

```js
const profiler = require('v8-profiler-node8')
profiler.startProfiling('', true);
setTimeout(function() {
  var profile = profiler.stopProfiling('');
  console.log(profile)
  profiler.deleteAllProfiles();
}, 1000);
```

### HEAP Snapshot API
`Snapshot.getHeader()` - provides short information about snapshot.

`Snapshot.compare(snapshot)` - creates HEAP diff for two snapshots.

`Snapshot.delete()` - removes snapshot from memory.

`Snapshot.export([callback])` - provides simple export API for snapshot. `callback(error, data)` receives serialized snapshot as second argument. (Serialization is not equal to `JSON.stringify` result).

If callback will not be passed, `export` returns transform stream.

`Snapshot.serialize` - low level serialization method. Look `Snapshot.export` source for usage example.

```js
var fs = require('fs');
var profiler = require('v8-profiler-node8');
var snapshot1 = profiler.takeSnapshot();
var snapshot2 = profiler.takeSnapshot();

console.log(snapshot1.getHeader(), snapshot2.getHeader());

console.log(snapshot1.compare(snapshot2));

// Export snapshot to file file
snapshot1.export(function(error, result) {
  fs.writeFileSync('snapshot1.json', result);
  snapshot1.delete();
});

// Export snapshot to file stream
snapshot2.export()
  .pipe(fs.createWriteStream('snapshot2.json'))
  .on('finish', snapshot2.delete.bind(snapshot2));
```

## CPU Profile API
`Profile.getHeader()` - provides short information about profile.

`Profile.delete()` - removes profile from memory.

`Profile.export([callback])` - provides simple export API for profile. `callback(error, data)` receives serialized profile as second argument. (Serialization is equal to `JSON.stringify` result).

```js
var fs = require('fs');
var profiler = require('v8-profiler-node8');
profiler.startProfiling('1', true);
var profile1 = profiler.stopProfiling();
profiler.startProfiling('2', true);
var profile2 = profiler.stopProfiling();

console.log(profile1.getHeader(), profile2.getHeader());

profile1.export(function(error, result) {
  fs.writeFileSync('profile1.json', result);
  profile1.delete();
});

profile2.export()
  .pipe(fs.createWriteStream('profile2.json'))
  .on('finish', function() {
    profile2.delete();
  });
```

## node-inspector

Cpu profiles can be viewed and heap snapshots may be taken and viewed from the
profiles panel.

---
_Source: https://npm.io/package/v8-profiler-node8 · Machine-readable twin of the npm.io package page. Health data is recomputed on every publish._