secondlife / secondlife/viewer
Bugsplat does not decode crash reports from Mac Project viewers.
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 299
- Forks
- 146
- Avg merge
- 1d 9h
- Merged PRs (30d)
- 88
Description
Environment
Second Life Project Gltf Mesh Import 7.1.14.15361077240 (64bit)
CPU: Apple M1 (2400 MHz)
Memory: 8192 MB
OS Version: macOS 15.5.0 Darwin 24.5.0 Darwin Kernel Version 24.5.0: Tue Apr 22 19:48:46 PDT 2025; root:xnu-11417.121.6~2/RELEASE_ARM64_T8103 x86_64
Graphics Card Vendor: Apple
Graphics Card: Apple M1
Description
Bugsplat does not decode crash reports from Mac Project viewers.
Reproduction steps
- Install a project viewer on Mac (eg. https://github.com/secondlife/viewer/releases/tag/Second_Life_Project%237aea88f-Gltf_Mesh_Import)
- Enable the the Develop menu in Preferences > Advanced.
- Force an error. Develop menu > Force an Error > Force LLError And Crash
- Start the viewer again so the crash report is sent to Bugsplat.
- Look at the crash report in Bugsplat. (eg. https://app.bugsplat.com/v2/crash?database=SecondLife_Viewer_2018&id=1634850)
Observed:
Expected: A properly decoded stack.
Note: This issue has been around since at least 2021 (old report: https://github.com/secondlife/jira-archive-internal/issues/63269)
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Reproduce the failure with the Mac Project viewer using Develop > Force an Error > Force LLError And Crash, then inspect the Bugsplat report linked in the issue and compare it with a correctly decoded stack. Trace the macOS crash-report submission and decoding path; done means Bugsplat displays a properly decoded stack for these crash reports.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp, macos
- Domain
- observability-sre
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 45/100