Keep the lesson for the next incident
Cluster the retention paths
Group cases by object URL, decoded pixels, canvas, worker, listener, hidden item, and error or reorder path. Record file dimensions, cycle count, release event, and the first visible user consequence for each cluster.
Document preview ownership
State which object owns each resource, when it is created, when replacement or removal releases it, and what remains shared intentionally. Include a small and large file cycle plus a page-exit comparison.
Add a lifecycle trigger
Require the cycle fixture when changing preview formats, thumbnails, workers, selection controls, validation, or navigation. Assign an owner for resource release and note any bounded cache policy that reviewers must distinguish from accidental retention.
What to carry forward
The learning record is complete when each preview resource has an ownership and release rule, a repeatable cycle fixture, and a known user consequence for failure. If memory tooling cannot name an owner, retain the observation as a bounded performance finding.
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