secondlife / secondlife/viewer

RenderUIBuffer debug setting - instant crash if set TRUE.

Open
#904 0 comments 0 reactions 1 assignee View on GitHub

@Geenz is already working on this.

Since Oct 30, 2025.

bug stale triage vr
Dominant language
C++
Stars
299
Forks
146
Avg merge
1d 9h
Merged PRs (30d)
88

Description

Environment

Second Life Release 7.1.3.7821226606 (64bit)
Release Notes

You are at 90.4, 16.3, 21.2 in Damiano located at simhost-0bba6d76d07a4f715.agni
SLURL: http://maps.secondlife.com/secondlife/Damiano/90/16/21
(global coordinates 262,234.0, 249,104.0, 21.2)
Second Life Server 2024-01-19.7590161929
Release Notes

CPU: Intel(R) Xeon(R) CPU E5-1620 v3 @ 3.50GHz (3491.92 MHz)
Memory: 32689 MB
OS Version: Microsoft Windows 10 64-bit (Build 19045.4046)
Graphics Card Vendor: NVIDIA Corporation
Graphics Card: NVIDIA GeForce GTX 1080/PCIe/SSE2

Windows Graphics Driver Version: 31.0.15.5161
OpenGL Version: 4.6.0 NVIDIA 551.61

Window size: 1289x881
Font Size Adjustment: 96pt
UI Scaling: 1
Draw distance: 512m
Bandwidth: 3000kbit/s
LOD factor: 3
Render quality: 6
Texture memory: 7291MB
Disk cache: Max size 1638.4 MB (100.1% used)

J2C Decoder Version: KDU v7.10.4
Audio Driver Version: FMOD Studio 2.02.13
Dullahan: 1.14.0.202310131404
CEF: 118.4.1+g3dd6078+chromium-118.0.5993.54
Chromium: 118.0.5993.54
LibVLC Version: 3.0.16
Voice Server Version: Vivox 4.10.0000.32327.5fc3fe7c.399bd0e

Packets Lost: 1/16,727 (0.0%)
February 29 2024 06:28:06

Description

Trying to set debug setting RenderUIBuffer true as an experiment and the viewer instantly crashes. Instant crash repeats on Firestorm 6.6.17 (pre-PBR viewer), so its unlikely to be related to recent PBR changes.

If this seting is no longer supported, it would be worth removing it.

Reproduction steps

Log in anywhere.
Use Debug setting to change RenderUIBuffer to TRUE.
Note instant crash.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.