Skip to content

Memory fixes - #21

Merged
naushir merged 3 commits into
mainfrom
memory
Oct 1, 2026
Merged

naushir merged 3 commits into
mainfrom
memory

Conversation

@naushir

@naushir naushir commented Oct 1, 2026

Copy link
Copy Markdown
Contributor

No description provided.

A failed chart search returned its exception, whose traceback reached every
calling frame and was kept alive in a cycle through the caller's message
local. Large image arrays and the camera itself then survived until the
cyclic collector ran, which rarely happens, so returning the message text
instead cuts a single target's peak from 12.7 GB to 6.7 GB for both targets.
ALSC frames now keep only their grid cell means, dark frames their channel
statistics, and Macbeth bursts their exact uint32 sums, from which lux
rebuilds the identical float64 average. Results are bit-identical, and a
50 MP run with both targets now peaks at 2.8 GB rather than 6.7 GB.
… resolution

The "Capture PNG (full res)" button had saved the downscaled preview frame since the
zero-shutter-lag change, so it now takes a still at the selected mode's resolution.
That still is held to the preview frame's exposure, gain, colour gains and ISP controls,
and the user's exposure and white balance settings are re-applied afterwards, so the
live preview no longer steps after a snapshot.
@naushir
naushir merged commit 45ebb22 into main Oct 1, 2026
2 checks passed
@naushir
naushir deleted the memory branch October 1, 2026 14:38
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant