LLImageRaw::sRawImageCount goes negative (-71,420) #162

Closed
opened 2026-09-29 05:49:03 +00:00 by sky_line · 1 comment
Owner

The VKMem log line reports raw imgs -71420. LLImageRaw::sRawImageCount is decremented more often than it's incremented: some constructor or copy / move path doesn't count, or a destructor path counts twice.

It's bookkeeping only (not a leak by itself), but it makes the counter useless for spotting the real raw-image leaks we care about for RAM (see the CPU texture copies ticket). Audit every LLImageRaw constructor, assignment and move, and the Vulkan path's raw handling, so the count matches live objects. Then log it next to cpu tex.

The VKMem log line reports `raw imgs -71420`. `LLImageRaw::sRawImageCount` is decremented more often than it's incremented: some constructor or copy / move path doesn't count, or a destructor path counts twice. It's bookkeeping only (not a leak by itself), but it makes the counter useless for spotting the real raw-image leaks we care about for RAM (see the CPU texture copies ticket). Audit every LLImageRaw constructor, assignment and move, and the Vulkan path's raw handling, so the count matches live objects. Then log it next to `cpu tex`.
Author
Owner

Verified: the VKMem line now reads a steady 'raw imgs ~7094' (was -71420). The missing increment was in the const-copy constructor (0415f39fe6).

Verified: the VKMem line now reads a steady 'raw imgs ~7094' (was -71420). The missing increment was in the const-copy constructor (0415f39fe6).
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
sky_line/Slipstream#162
No description provided.