Draw distance shortened for no apparent reason.

[Dan-Linden]

Environment

Second Life Release 7.2.2.17616393300 (64bit)
Release Notes

You are at 3.7, 127.9, 85.1 in LagLand located at simhost-098933e8d46984b92.agni
SLURL: http://maps.secondlife.com/secondlife/LagLand/4/128/85
(global coordinates 260,100.0, 248,192.0, 85.1)
Second Life Server 2025-07-25.16512260888
Release Notes

CPU: AMD Ryzen 9 5980HX with Radeon Graphics (3293.72 MHz)
Memory: 15775 MB
OS Version: Microsoft Windows 11 64-bit (Build 22631.5768)
Graphics Card Vendor: ATI Technologies Inc.
Graphics Card: AMD Radeon RX 6800M

Windows Graphics Driver Version: 30.0.15020.1001
OpenGL Version: 4.6.14800 Core Profile Context 21.50.20.01 30.0.15020.1001

Window size: 1640x1134
Font Size Adjustment: 96pt
UI Scaling: 1
Draw distance: 128m
Bandwidth: 3000kbit/s
LOD factor: 1.75
Render quality: 5
Texture memory: 11474MB
Disk cache: Max size 2150.4 MB (100.0% used)

J2C Decoder Version: KDU v7.10.4
Audio Driver Version: OpenAL, version 1.1 ALSOFT 1.24.2 / OpenAL Community / OpenAL Soft: OpenAL Soft
Dullahan: 1.14.0.202408091639
CEF: 118.4.1+g3dd6078+chromium-118.0.5993.54
Chromium: 118.0.5993.54
LibVLC Version: 3.0.21
Voice Server Version: Vivox 4.10.0000.32327.5fc3fe7c.5942f08

Packets Lost: 1/443 (0.2%)
September 11 2025 15:52:04

Description

The viewer draw distance shortened on the minimap and stayed there while draw distance in Preferences was still 128m. All the objects on the LagLand region disappeared.
There is a feature to shorten the draw distance to conserve memory when the viewer is in the background. It's as if that feature was engaged but did so while the viewer was in the foreground.

Reproduction steps

1. I was logged into LagLand.with 7.2.2.17616393300.
2. Then ???

Observed: The walls of objects started disappearing and the draw distance on the minimap became very short.

Log from that session: why did the objects just disappear SecondLife.log

---

This repo is using Opire - what does it mean? 👇

💵 Everyone can add rewards for this issue commenting /reward 100 (replace 100 with the amount).
🕵️‍♂️ If someone starts working on this issue to earn the rewards, they can comment /try to let everyone know!
🙌 And when they open the PR, they can comment /claim #4663 either in the PR description or in a PR's comment.

🪙 Also, everyone can tip any user commenting /tip 20 @Dan-Linden (replace 20 with the amount, and @Dan-Linden with the user to tip).

📖 If you want to learn more, check out our documentation.

[Dan-Linden]

Maybe #4604 triggered this?

[akleshchev]

Yes #4604 triggered.

2025-09-11T22:12:35Z WARNING # newview/llviewertexture.cpp(543) LLViewerTexture::updateClass : Low system memory detected, emergency downrezzing off screen textures

Current available physical memory: 474.46 MB
Threshold is set to 512MB, but there appears to be 33GB of avaliable page file memory, so I will modify #4604 to take page file into account. For now you can reduce RenderMinFreeMainMemoryThreshold to avoid the issue. But Low system memory would have triggered even without my changes, so we probably need to change the way we detect low memory in general.

[akleshchev]

Halved memory threshold and detached from bias, this might result in range decrease being more 'jumpy' when memory drops, but gives OS more time to compensate. Can improve on this later if range decrease does help with OOM crashes.

[Dan-Linden]

Passed QA.
Verified on Second Life Release 7.2.2.17774206511 on Win11/OSX in the scope of https://github.com/secondlife/iqa/issues/550

I don't know what the repro steps were, but this has not happened again during my testing.