secondlife / secondlife/viewer

Statistics window shows a lot of N/A stats

Open
#4,694 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

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

Description

Environment

Second Life Release 7.2.2.17774206511 (64bit)
Release Notes

You are at 137.5, 228.3, 133.6 in Linden Lab HQ 4 located at simhost-0f340ca0324a590c7.agni
SLURL: http://maps.secondlife.com/secondlife/Linden%20Lab%20HQ%204/137/228/134
(global coordinates 238985.0, 244196.0, 133.6)
Second Life Preflight 2025-08-21.17114312399
Release Notes

CPU: Apple M2 (2400 MHz)
Memory: 24576 MB
OS Version: macOS 15.7.0 Darwin 24.6.0 Darwin Kernel Version 24.6.0: Mon Aug 11 21:16:52 PDT 2025; root:xnu-11417.140.69.701.11~1/RELEASE_ARM64_T8112 arm64
Graphics Card Vendor: Apple
Graphics Card: Apple M2

OpenGL Version: 4.1 Metal - 89.4

Window size: 1338x782
Font Size Adjustment: 96pt
UI Scaling: 1.05
Draw distance: 96m
Bandwidth: 10000kbit/s
LOD factor: 1.125
Render quality: 1
Texture memory: 16384MB
Disk cache: Max size 2150.4 MB (100.0% used)
HiDPI display mode:

J2C Decoder Version: KDU v8.4.1
Audio Driver Version: OpenAL, version 1.1 ALSOFT 1.24.2 / OpenAL Community / OpenAL Soft: OpenAL Soft
Dullahan: 1.21.0.202508272158
CEF: 139.0.28+g55ab8a8+chromium-139.0.7258.139
Chromium: 139.0.7258.139
LibVLC Version: 3.0.21
Voice Server Version: Secondlife WebRTC Gateway

Packets Lost: 0/10712 (0.0%)
September 17 2025 09:06:02

Description

All frame time and jitter statistics are reported as n/a on my M2 based Macbook Air.

Image
Reproduction steps

log in and open the statistics window with command+shift+1


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 #4694 either in the PR description or in a PR's comment.

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

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

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.

Research direction

Start by reproducing the issue on macOS with the Statistics window opened via Command+Shift+1, then trace where the frame-time and jitter values are collected and displayed. Compare the M2 behavior with a platform where these statistics are populated. Done means the affected statistics show meaningful values instead of N/A.

Written by the indexing model from the issue text.

Assessment

Tech stack
cpp, macos
Domain
performance
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.