RAM: 16.7 GB of CPU texture copies kept after GPU upload #159
Labels
No labels
amd
avatars
bug
builder
cannot-reproduce
crash
epic
feature
from-viewer
gl-removal
known-limitation
monitoring
parity
perf
platform
priority
critical
priority
high
priority
low
priority
medium
provenance
rendering
rt
status
in-progress
status
testing
status
up-next
triage
ui
upstream
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Blocks
Reference
sky_line/Slipstream#159
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Users report excessive RAM use. A busy two-sim view (2026-09-29, ~45 avatars) measured 28.3 GB RSS (26.2 GB anonymous). The viewer's own accounting (
VKMemlog line,[cpu tex ...]):That's
LLImageGL::sVKCpuBytes: pixel copies retained so the Vulkan path can (re)upload textures. It's more than half the process, while the GPU holds only 3.4 GB of textures at the residency it actually uses.Direction (standard engine practice)
RenderVKCpuTexBudgetMB), rather than retaining every texture ever decoded.Check
cpu texin the VKMem line should fall from 16.7 GB to a small working set; RSS should drop by roughly the same.Refs #157 (perf/memory audit).
Part of #405 (RAM/VRAM management epic).
Ticket audit 2026-10-07: done and shipped in 1.0.0 Beta 10. CPU texture copies cut to thumbnails after upload, governor-trimmed, tiered, and served from the GPU-ready disk cache (
475bfa8d4f,0e64a5c9c1,d18a2f978f,3b69be27c5,2e46bbcecd). If you still see the problem on the current beta, please reopen or file a new report.