🪰 Viewer Bug Reports

• Use concise, precise descriptions• Do not include sensitive information. • Create a support ticket at https://support.secondlife.com for individual account issues or sensitive information.
WebRTC Voice connection problems
I see my dot - so I am connecting  too the server or it's a false connection ? I see no sound waves for myself - other avatars are in the RED; they can not hear me and I can't hear them. Was told to wait for a region restart-  I did nothing changed. Was sent the Wiki on sl voice trouble shooting - even though it did not apply too me, its trouble shoots the Vivox  system .     BUT humor them anyway and went through each step 1. by 1. too no avail Things I have tried on my own and with help from Tech friends Both Firestorm Viewer , current and Beta  The Current SLV viewer  tried them all . White listed the recommend files  in Windows Defender installed a different Anti virus , no change  ( Avast - and the firestorm is white listed in there) reinstalled all viewers-  from scratch , deleted everything off my pc! ( a long shot)  did not work !  i didn't think it would :) Tried other accounts on my PC  same as my main . Tried 2 other pc's in the house and worked fine.  so its not blocked in my router/firewall was told it used Port 443? then is open , if that is the port its using and was blocked why would it work on other pcs? I restarted the router and unplugged it and restarted pc ... I have been to the testing regions but it doesn't work.   the old voice system does work just fine its just the WebRTC that is the problem I was thinking it was My Pc where the problem is - but having talked to support again this am.  seems too think it may not be? I  have sent my logs to support . Which is where I am at now. submitting this to form as requested by support
11
¡
SL Viewer
¡
complete
LLThreadSafeQueue error during startup on Strix Halo (Windows)
On a new Strix Halo PC (AMD RYZEN AI MAX+ w/ Radeon 8060s) running Windows 11 Pro 25H2, the Second Life Viewer (along with Firestorm, Alchemy, and Megapahit viewers) hangs during startup during the 'Initializing Texture Cache dialog'. Cool VL Viewer (1.x based) and ApertureOS (skips startup checks) do not have this crash. The last entry (only apparent error) in the log is the line > WARNING #ThreadPool# llcommon/llthreadsafequeue.h(314) LLThreadSafeQueue<struct tagMSG,class std::queue<struct tagMSG,class std::deque<struct tagMSG,class std::allocator<struct tagMSG> > > >::push_ : ONCE: Threadsafe queue push_(lockacquired) queue full 1024 >= 1024 Multiple reinstalls of the viewer, exceptions added to windows defender whitelist, as well as a reinstall of Windows 11 have all been performed to no avail. For reference, this PC features 128GB 8000MT/s unified memory with 32GB allocated to the system and 96GB allocated to VRAM. SL and windows are installed and running from a 2TB Crucial Gen4 NVMe SSD. While this is probably currently an edge-case as these machines are not currently common in the market, AMD are looking to push more APU based computers in the near future and if this is due to the APU-based platform (relatively high core count at 16 Core / 32 thread, VRAM amount, or nature of unified memory) this could warrant investigation. Attached log from latest Firestorm initialization attempt.
7
¡
SL Viewer
¡
complete
Load More
→