User Journey… | nodejs/diagnostics

还没有人认领这个 Issue。

Start in the documentation folder and review issue #439 for the tutorials produced by the WG Deep Dive. Choose an unchecked tutorial from the list, following the linked llnode issue where relevant, and update this issue when the tutorial is completed. Done means the selected tutorial is transposed into a live document and its checklist entry is marked complete.

由索引模型根据 Issue 内容生成。

This issue aims to track the remaining tutorials under documentation folder.

The https://github.com/nodejs/diagnostics/issues/439 contains the documents created in the WG Deep Dive and we are working to transpose them into live documents.

Abnormal Termination
- Using exit stack traces
- Using diagnotics report
- Using valgrind
- Using llnode
CPU
- Monitoring Excessive CPU Usage
Crash
- What is a crash (intro)
- Using node report
- Using llnode (https://github.com/nodejs/llnode/issues/401)
Hang
- Using trace sigint
- Using Chrome DevTools
- Using node report
Live Debugging (https://github.com/nodejs/nodejs.org/pull/4772)
- Using Node Inspector
Memory (https://github.com/nodejs/nodejs.org/pull/4728)
- Using Heap Profiler
- Using Heap Snapshot
- Using GC Traces
- Using Native Tools
Poor Performance (https://github.com/nodejs/nodejs.org/pull/4928)
- Using V8 Profiler
- Using Linux Perf
Tracing
- Using Trace Events

Feel free to update this description when a tutorial is done.

cc: @nodejs/diagnostics

User Journey tracking documentation

评估

调研方向

描述

贡献指南

从这里开始

nodejs/diagnostics 的其他 Issue

相似的 Issue