FredApps 006dcc962d #1615: Auto caps CPU frames in flight from free memory after a job switches to the CPU (#3458) ...

A GPU project whose Render Queue job measured the CPU faster (#3335) rendered
every frame of a batch at once on the CPU, one per thread, with no memory cap:
on a 16-thread machine at about 1.4 GB a frame the app ran out of RAM and
exited without an error (0.23.1, Windows).

While a job renders on the CPU after a GPU frame measured its working memory,
CPU frames in flight now fit half the memory the system has free at that size
per frame, 1 to one per thread, settled once per job and logged. The probe's
timed CPU frames use the same cap. EFFECTCRAFT_CPU_INFLIGHT still overrides
it; Software Rendering projects, with no measurement, are unchanged. The host
reads the free memory through the new JobOptions::free_memory.

2026-11-11 14:31:36 +01:00

..

src

#1615: Auto caps CPU frames in flight from free memory after a job switches to the CPU (#3458)

2026-11-11 14:31:36 +01:00

tests/it

Add affected CI and replayable crash repros (#1224)

2026-11-10 14:57:32 +01:00

Cargo.toml

Effect ▸ Install Effect Plug-in… and plug-in bundles (wasm + ScriptUI panel in one go) (#2749)

2026-11-05 11:35:54 +01:00