Firestorm may crash after a failed teleport when switching the camera from Front View to Default View
needs info
Babie Boucher
Steps to Reproduce:
STEP 1: Enable Front View.
STEP 2: Switch the camera back to Default View.
STEP 3: Trigger a teleport failure.
Actual Result:
Firestorm crashes without any error message.
Expected Result:
The viewer remains running and displays the teleport failure message.
Impact:
The user must restart the viewer.
Additional Note:
The issue appears to be reproducible when switching from Front View to Default View before a failed teleport. The problem has been observed on multiple systems with different hardware configurations, making a hardware-related cause unlikely.
Environment
Firestorm Release: 7.2.4 Build 80712
Operating System: Windows 11 64-bit
Observed on multiple systems with different hardware configurations.
Log In
Dan Linden
updated the status to
needs info
Whirly Fizzle
So far I've been unable to reproduce this using Firestorm Viewer.
I did lots of teleports & before each TP I changed camera view to front view then back to default back view.
I experienced one TP disconnect & the viewer exited correctly after the disconnect.
I also deliberately triggered the TP throttle so further TP attempts were blocked & the viewer didn't crash.
Can you give more details about the type of TP failure you are getting that seems to trigger the crash?
Is it a TP disconnect or TP failure due to the destination region being full or something else?
I'm also not seeing any Bugsplat crashes from you on Firestorm.
Please can you make sure you have crash reporting enabled under Preferences -> Crash Reports & that "include username" is ticked, so I can find your crash reports.
Hecklezz Resident
Since you specify Firestorm specifically, have you tested if this occurs also on Linden Lab's official Second Life viewer? If you haven't, it would be best to test that if at all possible to confirm if this is a problem with LL's viewer too or only Firestorm. Otherwise if you have tested and the issue does not occur, then the issue should be brought up to Firestorm specifically and not LL (only once you confirm it is a Firestorm only issue)-