secondlife / secondlife/viewer

ExtraFPS crashes when RenderDebugGLSession is True

Open
#3,597 6 comments 0 reactions 1 assignee View on GitHub

@marchcat is already working on this.

Since Feb 25, 2025.

  • #3622 by @marchcat — merged
  • #3858 by @marchcat — merged
bug team:viewer
Dominant language
C++
Stars
299
Forks
146
Avg merge
1d 9h
Merged PRs (30d)
88

Description

Environment

Second Life Release 7.1.11.12363455226 (64bit)
Release Notes

CPU: Intel(R) Core(TM) i7-5930K CPU @ 3.50GHz (3491.92 MHz)
Memory: 32610 MB
OS Version: Microsoft Windows 10 64-bit (Build 19045.5487)
Graphics Card Vendor: NVIDIA Corporation
Graphics Card: NVIDIA GeForce GTX 1080/PCIe/SSE2

Windows Graphics Driver Version: 32.0.15.6590
OpenGL Version: 4.6.0 NVIDIA 565.90

Window size: 1725x1084
Font Size Adjustment: 96pt
UI Scaling: 1
Draw distance: 128m
Bandwidth: 3000kbit/s
LOD factor: 1.375
Render quality: 3
Texture memory: 8192MB
Disk cache: Max size 1638.4 MB (0.6% used)

J2C Decoder Version: KDU v7.10.4
Audio Driver Version: OpenAL, version 1.1 ALSOFT 1.23.1 / 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:

February 20 2025 15:57:19

Description

ExtraFPS crashes when RenderDebugGLSession is True, while the previous 2 releases (7.1.9.10515727195 - Atlasaurus, 7.1.10.10800445603 - DeltaFPS) worked fine.

Reproduction steps
  1. Start the viewer
  2. Enable Me > Preferences > Advanced > Show Advanced Menu. This shows the Debug menu on the login screen.
  3. Debug menu > Show Debug Setting. Set RenderDebugGLSession to TRUE
  4. Quit the viewer
  5. Start the viewer
  6. Log in

Observed: The viewer crashes.

Windows: 7.1.11.12363455226 - ExtraFPS SecondLife.log
Last line: 2025-02-21T00:08:25Z ERROR # llrender/llglslshader.cpp(1262) LLGLSLShader::disableTexture : Texture channel 7 texture type corrupted.

Mac, which crashes before reaching the login screen: Mac M1 ExtraFPS SecondLife.log

Expected: The viewer should not 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.