← FAQ hub

FAQ · P1

Large Electron / ASAR & JS graphs

Silent minutes, RangeError, and MCP sessions that stop answering pings.

Symptoms

• analyze-javascript-application on a multi‑tens‑of‑MB ASAR prints nothing for a long time, then fails generically.
• Huge in-memory graphs blow string limits (RangeError: Invalid string length) masked as I/O errors.
• While JS analysis runs synchronously, MCP ping/cancel may appear wedged.

Working pattern

1. Start with a smaller loader or extracted subset, not the whole ASAR.
2. Stage questions: inventory → one feature → one module.
3. Watch doctor/client health; restart the MCP session after a hard abort.
4. Prefer CLI for elephantine targets when the interactive agent needs to stay responsive.

Authorized builds only — your app, your CI artifact, or permissioned samples.