Frontend Developer interview prep for Adobe.

1. Decouple input sampling from rendering: capture pointer events via `pointermove` and record coordinates in an array; do not draw directly in the event handler. 2. Synchronize rendering with `requestAnimationFrame`, consuming pending points in one batch per frame. 3. Smooth raw input coordinates using quadratic Bezier curves or Catmull-Rom splines to prevent jagged lines. 4. Layering strategy: draw in-progress brush strokes on an active transparent canvas layer, and bake completed strokes down into a persistent background bitmap buffer on `pointerup`. 5. Minimize garbage collection pauses by reusing vector point objects instead of instantiating new objects on every move event.

Open Chrome DevTools Memory panel and record three Heap Snapshots: baseline, after performing an editing action, and after closing the document. Filter by 'Detached' in the Class filter to identify detached DOM nodes or canvas textures retained by closures, global event listeners (e.g., `window.addEventListener`), or singleton store observers. Inspect the Retainers tree to locate the root reference preventing garbage collection. Fix by ensuring every subscribed listener is explicitly removed in teardown lifecycles (`disconnectedCallback` or `useEffect` cleanup) and nullifying references to large canvas contexts and buffers.