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.