lodestar-heapsnapshots

You can capture a Lodestar heap snapshot by triggering the REST write_heapdump endpoint via SSH. This allows you to remotely write heap dumps for specific threads like main, network, and discv5 to a designated output directory.

To analyze a Lodestar heap snapshot for memory leaks, use the bundled Node.js script to diff two captured snapshots. This highlights significant growth in object types and counts to pinpoint the source of the leak.

Debugging Lodestar memory leaks involves capturing heap snapshots before and after a period of activity, then diffing them. This Skill automates capturing from running beacon nodes and analyzing the diff to identify memory growth patterns.

Yes, capturing Lodestar heap dumps requires SSH access to the host machine. You also need a reachable Lodestar REST API and knowledge of the snapshot output directories to successfully write and retrieve the dumps.

Yes, you can capture heap snapshots for specific Lodestar threads including main, network, and discv5. By targeting the write_heapdump endpoint, you can isolate memory leak investigations to individual beacon node components.

Increasing memory usage in Lodestar often indicates a memory leak. Use this Skill to capture and diff heap snapshots from your running beacon node, highlighting significant object growth to identify the exact source of the leak.