Claude d247b98b95 Viewer: dragging a layer no longer piles up frame renders until memory runs out (#647) ...

Every viewer request spawns a job on the frame pool. A pool thread blocked
inside a render (waiting on a parallel loop's join) runs other pool work
meanwhile, rayon's injected jobs included: the spawn of the next request
started a whole frame render on top of the waiting one. Dragging makes a
new revision, and a new viewer frame, every UI frame, so renders nested
without bound on every thread, each holding its buffers (a large image's
full-resolution copies), until all memory was used. Holding the layer still
makes no new revisions, which is why only moving it did this.

A spawn now drains the queue, and one that lands inside a render on its
thread returns at once; the render below takes the queued jobs when it is
done. Each pool thread renders one frame at a time.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01QiAJeFttZp83Fh7YuzAR5f

2026-10-10 23:29:44 +00:00

..

examples

Merge main into menu-parity branch; point AE menu entries at main's real commands

2026-10-02 00:12:01 -04:00

src

Viewer: dragging a layer no longer piles up frame renders until memory runs out (#647)

2026-10-10 23:29:44 +00:00

tests

Community follow-ups: dedup font files from overlapping folders (#665); empty-Timeline drop also accepts compositions, rustfmt (#662)

2026-10-10 22:29:04 +00:00

build.rs

About: contributor and model credits compiled in (grab bag + table, self-submitted names) (#228)

2026-10-07 21:16:47 -04:00

Cargo.toml

Effects: EXtractoR picks layers and channels of multi-layer EXRs (#295)

2026-10-09 17:32:09 +07:00