Files
software-mansion__argent/packages/tool-server/test/ios-instruments/report-table-pipe-escape.test.ts
Ignacy Łątka a5c6730d05 feat(ios-profiler): attributable memory leaks via malloc_stack_logging (#351)
## What

Opt-in `malloc_stack_logging` flag on `native-profiler-start` that makes
iOS memory leaks **attributable** — they come back with a real
responsible frame + library instead of `<Call stack limit reached>`.

## Why

`native-profiler-start` attaches to the already-running app. iOS records
malloc allocation backtraces only when `MallocStackLogging` is set **at
process launch**, so an attached app has none: Instruments' Leaks
scanner finds the leaked blocks but can't attribute them and emits the
placeholder `<Call stack limit reached>` (that string is Instruments',
not ours).

## How

When `malloc_stack_logging: true`, the profiler cold-launches the app
**under** xctrace instead of attaching:

```
xctrace record --template <Argent.tracetemplate> --device <udid> \
  --env MallocStackLogging=1 --output <…> --no-prompt \
  --launch -- <App.app>
```

- `.app` path resolved via `simctl get_app_container`; the running
instance is terminated first for a clean cold start.
- The existing Leaks export / parser / render path is reused
**unchanged** — no parser changes.
- Default behaviour is untouched: attach to the running app (no
relaunch, no overhead). The flag is opt-in because it restarts the app
(loses state) and adds allocator overhead — for leak-attribution passes,
not CPU/hang work.
- The report relabels unattributable leaks with a hint to re-run with
`malloc_stack_logging: true`, instead of surfacing the raw placeholder.

## Evidence (real iPhone 16 sim, same scroll workload)

Before (attach) — every leak row:
```
responsible-frame="<Call stack limit reached>" responsible-library=""
```
After (`--env MallocStackLogging=1 --launch`) — same Leaks export:

| leaked-object | responsible-frame | library |
|---|---|---|
| Malloc 1008 B ×3 | `itanium_demangle::OutputBuffer::grow(...)` |
libc++abi |
| Malloc 48 B ×1 | `hermes::vm::JSTypedArrayBase::createBuffer(...)` |
hermes |

## Tests

- `test/ios-instruments/malloc-stack-logging.test.ts` — the malloc
launch argv (`--env MallocStackLogging=1`, `--launch -- <app>` last,
with and without `--notify-tracing-started`, `--no-prompt`) vs default
`--attach`; terminate-first / get_app_container ordering; failed-start
behavior; per-test `ARGENT_IOS_CAPTURE` scrubbing.
- `test/ios-instruments/leak-attribution-render.test.ts` —
unattributable vs attributed leak rendering, capture-mode-aware hints.
- `test/ios-instruments/load-freshness.test.ts` — per-capture residue
clearing on `profiler-load`, live/recovery-pending load refusals.
- `test/ios-instruments/stop-recovery.test.ts` — capture-mode pairing at
stop (clean and recovery paths).
- `test/profiler-combined-leaks.test.ts`,
`test/profiler-leak-stacks.test.ts`, `test/ios-leak-pipeline.test.ts` —
shared caveat line, evidence-first hints, attribution-normalized
grouping.
- Full `test/ios-instruments/` suite green (9 files / 70 tests); full
tool-server suite green; `tsc --noEmit` + `tsc -p tsconfig.test.json`
clean.

## Notes

E2E'd live twice during review (real iPhone 16 Pro / iPhone 17 Pro sims
on Xcode 26.6): guard refusals fire before the app is touched, the
`--device` cold launch's deadlock on degraded Xcode is confirmed (so the
guard is warranted), and the malloc argv/terminate/relaunch behavior
checked out on-device. Docs updated: `IOS_PROFILER_REFERENCE.md` and the
`argent-native-profiler` skill.

## Review follow-ups (post-approval hardening)

Later commits address the remaining review threads and several
subsequent multi-lens review passes:

- **Capture-mode is a real signal, end to end.** The session records the
mode of the in-flight recording at start
(`recordingMallocStackLogging`), pairs it with `exportedFiles` at stop
(`mallocStackLogging`), and freezes it into `parsedData` at analyze/load
— so the analyze report, the combined report, and the `leak_stacks`
drill-down all name the capture mode of the data they actually render
instead of inferring it (or mislabeling it after a newer capture
starts). One shared `renderUnattributedLeaksNote()` keeps the wording
identical across reports, and attribution evidence outranks the flag: a
resolved frame proves the target ran under malloc stack logging however
it was launched.
- **`profiler-load` restores a clean slate.** Loading clears all
per-capture residue (capture mode, `cpuFilterPid`, `wallClockStartMs`,
`traceFile`) so a loaded trace is never analyzed with a previous live
capture's PID filter, freshness anchor, or report path — and refuses to
load while a recording is in flight or a crashed capture awaits
`native-profiler-stop`'s partial-trace recovery, which the load would
otherwise orphan.
- **Failed starts are non-destructive.** Per-capture descriptors — and
the recovery flags that gate `native-profiler-stop`'s partial-trace
export — are stamped/reset only on a successful start, so a failed
attempt leaves the previous capture's still-loaded exports fully
described and a pending abnormal-end recovery intact.
- **Guards keep session state coherent.** `profiler-load`,
`native-profiler-analyze`, and `profiler-combined-report` all refuse
while a recording is in flight or a crashed capture awaits recovery, via
one shared `isCaptureInFlight`/`inFlightGuardMessage` helper whose
message distinguishes recording vs 10-min-cap timeout vs unexpected exit
(so the stated cause matches what `native-profiler-stop` reports next).
Proceeding would otherwise wedge the session (load) or render one
capture's frozen data under another's live fields (analyze/combined).
- **The combined report anchors on a frozen clock.** The recording's
start time is frozen into `parsedData` at analyze, and the iOS combined
report anchors its hangs to that frozen value rather than the live
session field — so a capture started after analyze can never shift a
real hang↔commit correlation into "unmatched". Android keeps its live
anchor (it re-derives hangs from the live trace). The combined-report
guard's recovery advice routes through `native-profiler-analyze`, the
only step that rebuilds `parsedData`.
- **Leak grouping is attribution-normalized.** `aggregateLeaks` keys on
`(objectType, frame-normalized-the-way-isLeakAttributed-matches)`, so
mixed unattributed spellings (`Unknown`, the sentinel, whitespace
variants) can't split one group per type.
- **The malloc launch target is unambiguous.** Since the cold launch
terminates the resolved app, `app_process` resolution prefers an exact
`CFBundleExecutable` match and, when builds still tie (dev + prod
sharing an executable/display name), refuses and points at the
globally-unique `CFBundleIdentifier` — which it also accepts as an
`app_process` — instead of killing whichever app the plist enumerates
first.
- **Report tables escape `|`.** Demangled C++ frames (`operator|`
included) are real headline content under malloc mode; every free-form
cell across the leak, CPU-hotspot, function caller/callee, and
thread-breakdown tables — symbol *and* thread/queue-name columns — is
escaped so a stray pipe can't shift the row's columns.
- **Android start is non-destructive too.** `startNativeProfilerAndroid`
now starts perfetto before mutating session state, mirroring iOS, so a
failed start no longer burns a prior capped capture's pending
partial-trace recovery.
2026-07-12 13:42:23 +02:00

129 lines
5.4 KiB
TypeScript

import { describe, it, expect } from "vitest";
import { renderNativeProfilerReport } from "../../src/utils/ios-profiler/render";
import {
renderFunctionCallersIos,
renderThreadBreakdownIos,
} from "../../src/tools/profiler/query/profiler-stack-query";
import type { ProfilerPayload, CpuSample } from "../../src/utils/ios-profiler/types";
import type { CpuHotspot } from "../../src/utils/profiler-shared/types";
// GFM splits a table row on every unescaped `|`, even inside a code span, so a
// demangled C++ frame such as `folly::operator|(...)` injects phantom columns
// and misaligns every cell after it. escapeMarkdownTableCell fixes this, but the
// leak tables were the only cells escaped initially — these tables interpolate
// the SAME demangleSymbol() output. dominantFunction is a real demangled frame
// in every capture mode (unlike leak frames, which need malloc_stack_logging),
// so a C++ operator| hotspot reaches all of them without any special setup.
const OP_FRAME = "folly::operator|(folly::Range<char const*>, folly::Range<char const*>)";
// Splitting on unescaped pipes must give the row the same column count as its
// header — the whole point of escaping.
const unescapedCells = (s: string) => s.split(/(?<!\\)\|/).length;
function hotspot(dominantFunction: string, thread = "Main Thread"): CpuHotspot {
return {
type: "cpu_hotspot",
platform: "ios",
dominantFunction,
totalWeightMs: 1234,
weightPercentage: 42,
sampleCount: 99,
thread,
severity: "RED",
topCallChain: [],
topCallChains: [],
duringHang: false,
timeRangeMs: { first: 0, last: 1000 },
burstWindows: [],
};
}
function sample(threadFmt: string, stackNames: string[]): CpuSample {
return {
timestampNs: 0,
threadFmt,
weightNs: 1_000_000,
stack: stackNames.map((name) => ({ name, isSystemLibrary: false })),
};
}
describe("report table pipe-escaping (finding 5: beyond the leak tables)", () => {
it("escapes a demangled operator| frame in the CPU Hotspots summary table", async () => {
const payload: ProfilerPayload = {
metadata: { traceFile: null, platform: "iOS", timestamp: "2026-07-09T00:00:00Z" },
bottlenecks: [hotspot(OP_FRAME)],
};
const res = await renderNativeProfilerReport({ payload, traceFile: null });
const header = res.report.split("\n").find((l) => l.startsWith("| # | Function | Thread"));
const row = res.report.split("\n").find((l) => l.includes("folly::operator"));
expect(header).toBeDefined();
expect(row).toBeDefined();
expect(row).toContain("operator\\|");
expect(unescapedCells(row!)).toBe(unescapedCells(header!));
});
it("escapes operator| in the function Called By / Calls Into tables", () => {
// "target" is called by op| and calls into op| — both caller and callee
// cells carry the pipe.
const samples = [
sample("Main Thread", ["callee", "target", OP_FRAME]),
sample("Main Thread", [OP_FRAME, "target", "callee2"]),
];
const out = renderFunctionCallersIos(samples, "target", 10);
const header = out.split("\n").find((l) => l === "| Function | Samples |");
expect(header).toBeDefined();
const rows = out.split("\n").filter((l) => l.includes("folly::operator"));
expect(rows.length).toBeGreaterThan(0);
for (const row of rows) {
expect(row).toContain("operator\\|");
expect(unescapedCells(row)).toBe(unescapedCells(header!));
}
});
it("escapes operator| in the per-thread Hotspots table", () => {
const samples = [sample("Main Thread", ["target"])];
const out = renderThreadBreakdownIos(samples, [hotspot(OP_FRAME, "Main Thread")], "Main", 10);
const header = out.split("\n").find((l) => l.startsWith("| Function | Weight (ms)"));
const row = out.split("\n").find((l) => l.includes("folly::operator"));
expect(header).toBeDefined();
expect(row).toBeDefined();
expect(row).toContain("operator\\|");
expect(unescapedCells(row!)).toBe(unescapedCells(header!));
});
// Pass-5 finding 1: the Function column was escaped but the sibling Thread
// column in the same tables was not. Dispatch-queue / thread names are
// developer-controlled strings and can contain '|'.
const PIPE_THREAD = "com.example|worker";
it("escapes a '|' in the CPU-Hotspots table Thread column", async () => {
const payload: ProfilerPayload = {
metadata: { traceFile: null, platform: "iOS", timestamp: "2026-07-09T00:00:00Z" },
bottlenecks: [hotspot("plainFunc", PIPE_THREAD)],
};
const res = await renderNativeProfilerReport({ payload, traceFile: null });
const header = res.report.split("\n").find((l) => l.startsWith("| # | Function | Thread"));
const row = res.report.split("\n").find((l) => l.includes("com.example"));
expect(header).toBeDefined();
expect(row).toBeDefined();
expect(row).toContain("com.example\\|worker");
expect(unescapedCells(row!)).toBe(unescapedCells(header!));
});
it("escapes a '|' in the Thread CPU Breakdown table Thread column", () => {
const samples = [sample(PIPE_THREAD, ["target"])];
const out = renderThreadBreakdownIos(samples, [], undefined, 10);
const header = out.split("\n").find((l) => l.startsWith("| Thread | Weight (ms)"));
const row = out.split("\n").find((l) => l.includes("com.example"));
expect(header).toBeDefined();
expect(row).toBeDefined();
expect(row).toContain("com.example\\|worker");
expect(unescapedCells(row!)).toBe(unescapedCells(header!));
});
});