Aglet

Prioritize preview memory growth by workflow duration

Memory behavior matters most in long-lived selection flows that handle large images or many replacements. Prioritization should use a reproducible sequence and observed user consequence, separating a delayed release from growth that prevents later files from being previewed during the same session.

Decide where the work belongs

  1. Describe the blocked workflow

    Record how many selections precede visible slowdown, failure, reload, or lost form state. Note file dimensions and preview mode, and distinguish a temporary rendering pause from sustained growth that prevents the user from finishing.

  2. Map lifecycle paths

    List selection, replacement, removal, reordering, validation, navigation, and error paths that create previews. Mark which paths release resources and which leave the item hidden or detached, using observations rather than assumed implementation.

  3. Choose the queue

    Queue resource-lifecycle repair when retained objects are identified, preview design review when the workflow intentionally keeps too much data, or measurement work when growth is observed without ownership evidence. Attach the shortest failing sequence.

What to carry forward

Prioritize the issue when repeated preview use can block completion or discard work in a session that should remain open. A bounded allocation that returns after release belongs behind sustained growth tied to a common file-selection path.

Technical background: MDN reference.

Keep the decision with the work.

Use a Work Item in Aglet to record the problem, the evidence you have, and the next decision. Add an owner and priority, then keep updates in the discussion so the next person can follow the reasoning.

Create an account See the product workflow