Pimp My IDE / garage dispatchBack to the garage
October 12, 2026 / browser memory / Chrome DevTools

Find what holds the weight.

A large object is not the diagnosis. The useful question is why it stayed reachable after the action was reversed.

Measure the cycle. Follow the retaining path. Name the code that owns the reference.

Agents can read the heap now.

Chrome's October DevTools recap says the Chrome DevTools MCP server can query heap objects by retained size or property name. It can also inspect edge sizes and memory held by V8 execution contexts.[1]

The current tool reference exposes a larger memory set behind the experimental --memoryDebugging=true flag. The documented tools compare snapshots, list retainers, search retaining paths, inspect dominators, find duplicate strings, and query objects by class, property, size, type, or detached state.[2]

Search narrows the heap. It does not explain the leak.

Retained size answers one question.

Chrome defines shallow size as the memory held by an object itself. Retained size is the memory that can be freed when that object and its dependents are no longer reachable.[3] A small listener or closure can therefore keep a much larger graph alive.

Sorting by retained size is a good way to find heavy suspects. It is not proof that the top object is wrong. A cache, application shell, or long-lived model can be large by design. The diagnosis needs an expected lifetime, a repeatable action, and a path back to a root.

Use a reversible cycle.

Chrome's manual workflow starts with a snapshot, runs an operation, reverses it, repeats the pair, then compares another snapshot with the first. Opening and closing the same document should not leave a fresh copy of its object graph behind each time.[3]

Keep the sequence exact. Record the route, fixture, browser build, cycle count, idle wait, and snapshot files. If garbage collection, timers, network responses, or animation can change the result, state that in the packet. One before-and-after pair may contain warm-up allocations that never grow again.

Follow ownership, not resemblance.

The heap view can show retainers for a selected object. The agent tool reference also documents retaining paths and dominator chains. Those routes help answer which live object prevents collection. They do not prove which source line created the reference unless the evidence reaches a named closure, property, listener, cache, or framework owner.

Turn the finding into a code review target. Name the retained object. Save its node identifier for that snapshot. Record the shortest useful retaining path. Point to the owner that should release it. Then rerun the same cycle after the fix and compare growth across several repetitions.

Interactive makeover / memory retainer winch

Rig the comparison.

This replaces a one-shot "memory high" badge with a repeatable cycle, a visible retaining path, and a copyable investigation packet. It drafts the test. It does not capture a heap or diagnose a leak.

BaselineExerciseReverseCompare

Cycle setup

Choose a repetition count, then select the evidence clauses that the test will require.

Open and close cycles4 cycles
1 warm-up check8 growth checks

Retainer map

The diagram shows the evidence route. It is not live browser telemetry.

GC ROOT / LIVE CONTEXT
EVENT
LISTENER
NAMED
CLOSURE
CACHE
PROPERTY
PAYLOAD / EXPECTED TO DIEObject identity, retained size, and owner are required from a real snapshot.
Test load / 4 cycles0 of 4 clauses
Four clauses are open.The cycle count is set. The investigation packet still needs its evidence requirements.
Sources read / October 12, 2026

Source log

Open the evidence boundary
  1. Chrome for Developers, "New in DevTools - October 2026", published September 22 and read October 12, 2026. Google documents heap object queries, edge filtering, size sorting, context analysis, and other Chrome 153 and 154 changes.
  2. Chrome DevTools MCP tool reference at commit 69524f0, committed and read October 12, 2026. The reference documents 14 memory tools, their parameters, and the experimental memory-debugging flag. This is the repository's current main branch, not proof that every published package contains the same set.
  3. Chrome DevTools, "Record heap snapshots", last updated February 9, 2024 and read October 12, 2026. Google defines shallow and retained size, snapshot comparison, retainers, reachable objects, and the action-reverse-repeat workflow.
  4. ChromeDevTools/chrome-devtools-mcp at commit 69524f0, read October 12, 2026. The repository describes live-browser inspection and warns that connected clients can inspect and modify browser data.

Evidence boundary: this page read the current documentation and pinned repository source. It did not install the package, connect it to Chrome, capture a heap snapshot, or reproduce a leak. The interactive winch creates a test packet only. A completed packet structure does not mean a browser run passed.