https://github.com/zhangyuang/v8-profiler-rs
Analyze V8 HeapSnapShot By Rust
https://github.com/zhangyuang/v8-profiler-rs
heapsnapshot rust v8
Last synced: about 1 month ago
JSON representation
Analyze V8 HeapSnapShot By Rust
- Host: GitHub
- URL: https://github.com/zhangyuang/v8-profiler-rs
- Owner: zhangyuang
- License: mit
- Created: 2022-01-17T11:55:18.000Z (over 3 years ago)
- Default Branch: main
- Last Pushed: 2025-03-09T07:57:43.000Z (2 months ago)
- Last Synced: 2025-03-28T20:06:54.569Z (about 2 months ago)
- Topics: heapsnapshot, rust, v8
- Language: Rust
- Homepage: https://v8.ssr-fc.com/
- Size: 35.7 MB
- Stars: 198
- Watchers: 8
- Forks: 6
- Open Issues: 0
-
Metadata Files:
- Readme: README.md
- License: LICENSE
Awesome Lists containing this project
README
[English](./README.md) | [็ฎไฝไธญๆ](./README_Zh.md)
# Introduction
[v8-profiler-rs](https://github.com/zhangyuang/v8-profiler-rs) is a project developed in `Rust` for intelligent online analysis of `V8 heapsnapshot` files. It helps developers using V8-based applications like `Node.js/Chrome/Deno/Electron` to better understand program memory structure and assist in locating memory leaks.
## How to start
Recommend using [Online Demo](https://v8.ssr-fc.com/), it's more convenient. Or you can start it in local.
```bash
$ git clone https://github.com/zhangyuang/v8-profiler-rs.git
$ cd v8-profiler-rs/example
$ yarn && yarn start
```
## Online Demo
We have deployed an [online website](https://v8.ssr-fc.com/) where you can upload and analyze V8 memory snapshots in real-time. We recommend using `Safari` or `Firefox` browsers, as `wasm` execution performance is significantly better than in `Chrome` .
## Default example
View default example by clicking the `Example` button on the top left corner.
The code of default example is as follows:
```js
const express = require('express');
const app = express();
const fs = require('fs')
// the memory leak code
let theThing = null;
let replaceThing = function() {
let leak = theThing;
let unused = function() {
if (leak)
console.log("hi")
};
theThing = {
bigNumber: 1,
bigArr: [],
longStr: new Array(1000000),
someMethod: function() {
console.log('a');
}
};
};
let index = 0
app.get('/leak', function closureLeak(req, res, next) {
replaceThing();
index++
if (index === 1) {
const stream = require('v8').getHeapSnapshot()
stream.pipe(fs.createWriteStream('small-closure.heapsnapshot'))
}
if (index === 40) {
const stream = require('v8').getHeapSnapshot()
stream.pipe(fs.createWriteStream('medium-closure.heapsnapshot'))
}
if (index === 50) {
const stream = require('v8').getHeapSnapshot()
stream.pipe(fs.createWriteStream('big-closure.heapsnapshot'))
}
res.send('Hello Node');
});
app.listen(3001);
```
## Analyze Report
There are two types of reports: single report and compare report.
### Single Report
```yml
Analyze Report with single
Only show nodes with more than 20 occurrences
Memory retained by constructor type
closure: 156409.05 MB
Object: 156408.32 MB
system / Context: 154881.33 MB
array: 4579.70 MB
synthetic: 1533.60 MB
Array: 1526.16 MB
WeakMap: 1526.01 MB
(compiled code): 2.96 MB
string: 2.10 MB
There are some nodes that are duplicated too many times
someMethod @70761: 202(memoryleak - demo / closure / index.js)
HttpError @95957: 44(node_modules / http - errors / index.js)
parse @89241: 33(node_modules / ms / index.js)
ClientError @50469: 31(node_modules / http - errors / index.js)
indexOf @49211: 27(node_modules / object - inspect / index.js)
send @126827: 23(node_modules / send / index.js)
resolve @98543: 23(node_modules / express / lib / view.js)
```
### Compare Report
```yml
Analyze Report with compare
Only show nodes with more than 20 occurrences
Additional nodes by constructor type
(compiled code): 242
ArrayBuffer: 127
system / JSArrayBufferData: 127
Buffer: 126
Node / std::basic_string: 78
closure: 69
Array: 46
array: 44
system / Context: 34
Object: 29
Bigger nodes by constructor type
(compiled code): 48
closure: 25
Bigger nodes by increased size
@1: +83.54 MB
Object @6613: +76.30 MB
Array @154471: +76.30 MB
Array @154499: +76.30 MB
app @6603: +76.30 MB(node_modules / .pnpm / express @4 .18 .2 / node_modules / express / lib / express.js)
router @6533: +76.30 MB(node_modules / .pnpm / express @4 .18 .2 / node_modules / express / lib / router / index.js)
closureLeak @6481: +76.30 MB(memoryleak - demo / closure / index.js)
Route @6511: +76.30 MB
Layer @6517: +76.30 MB
Layer @6497: +76.30 MB
Server @6609: +76.30 MB
system / Context @6483: +76.30 MB
```
## Implemented Features
๐ indicates implemented features. This application is continuously being updated, and updates will be synchronized to the README.md. Please stay tuned. If this application helps you, please give it a Star โจ
| Milestone | Status |
|-----------|--------|
| Parse V8 snapshot to generate complete node information | ๐ |
| View node source location and constructor | ๐ |
| Generate analysis reports | ๐ |
| Frontend visualization support | ๐ |
| Filter nodes by ID and name | ๐ |
| Filter number of nodes and view detailed node references | ๐ |
| Filter reference depth and number of references | ๐ |
| Compare two snapshot files | ๐ |
| Support two comparison types: new nodes/increased GC size | ๐ |
| Automatically filter non-business nodes based on node count | ๐ |
| Support uploading local serialized JSON files | ๐ |
| Implement `Wasm + WebWorker` parsing to avoid site unresponsiveness | ๐ |
| Optimize parsing performance and reduce memory usage | ๐ |
## Why Rust
Parsing V8 memory snapshots involves a lot of computational operations. CPU-intensive scenarios are inherently not JavaScript's strong suit.
After reading Chrome's official memory analysis tool source code, I found it uses many tricks to ensure performance, making the code highly complex and difficult to maintain.
Rust is perfect for this scenario, providing excellent performance while maintaining code readability. Rust's superior multi-threading capabilities are exactly what we need, as parsing computation logic is ideal for multi-threaded optimization. We will continue optimizing computational performance in future versions.
This application's approach can be applied to any programming language with GC. We will strive to support memory analysis for more programming languages in the future.
Finally, Rust's official WebAssembly support is excellent, allowing us to easily compile Rust code to WebAssembly for browser use.
## Handling Parse Timeout Issues
For very large files, you may encounter Wasm memory overflow or long parse times. If this occurs, try using `Safari` or `Firefox` browsers.
## Contact
The prohect has been updating, if you have any questions or suggestions, please submit an [issue](https://github.com/zhangyuang/v8-profiler-rs/issues)
### How to sponsor me
There are two ways to sponsor me both Alipay and WeChat
Eth address: 0x87a2575a5d4dbD5f965e3e3a3d20641BC9a5d192
## How to use
Open the [online demo](https://v8.ssr-fc.com/) and upload the `heapsnapshot` file. You can upload one or two files for comparison.
There will render heapsnapshot nodes in web page.
The node fields are as follows:
```js
{
"node_type": string; // node type
"name": string; // node name
"id": number; // node id
"size": number; // node self size
"edge_count": number; // node edge count
"retained_size": number; // node retained size, the free size of the node after GC
"pt": number; // the ratio of self size / retained size
"edges": {
"edge_type": string; // edge type
"to_node": number; // the id of the node that the edge points to
"name_or_index": string; // the name or index๏ผfor array๏ผ of the edge
} [];
"source": string; // the source file of the node
"constructor": string; // the constructor of the node
"percent": string; // the retained size ratio of the node
}
```