Bugsplat error messages

[KarraSue]

This morning While on Firestorm I received 2 "Bugsplat" popups saying an error caused the program to close. Are there any issues going on?

[AmeliaJ08]

This is the wrong forum, this is for the Second Life server.

I can answer though, you're probably encountering bug FIRE-34201: https://jira.firestormviewer.org/browse/FIRE-34201?jql=text ~ "bugsplat" ORDER BY created DESC%2C creator DESC

It affects the current release Firestorm 7.1.9-74745, the effect is a hard crash with a bugsplat message and after teleporting around a little. There's an explanation for it but the fix for the moment is to disable mirrors in the graphics preferences panel, this will solve the issue.

The bug is also fixed in recent Firestorm alpha versions if you do wish to leave mirrors turned on, you can get the download link for these by joining the "Firestorm preview group" in world group, the links for the latest alpha are in the notices.

I believe if you need to use mirrors in the current release 7.1.9-74745 it is probably best to enable them as needed and then disable it when you are done, I think this will avoid the risk of a crash.

If you're interested the cause of the bug is mentioned here along with the code that should fix it: https://github.com/FirestormViewer/phoenix-firestorm/commit/b225399a7dcf661855e84f553b12abdcf910362f

Quote

Multiple different crashes seemingly caused by a long  dead volume pointer.
Matches multiple bug splat ids.
Trigger details: have a mirror present and working. TP away, TP to a few other places. Importantly, the other places should not have any mirrors.
TP back to mirror. I believe that because the probe was never overwritten by another, upon return the code tries to reuse it only to find that the pointer is garbage.
The fix tries to ensure that the associated refelction map is cleaned up when the probe goes out of scope.

 

Edited August 19 by AmeliaJ08

[KarraSue]

I am not on Firestorm 7.1.9.71745. I am on 6.6.17.70368. 

[Faithless Babii]

On 8/20/2024 at 12:52 AM, KarraSue said:

I am not on Firestorm 7.1.9.71745. I am on 6.6.17.70368. 

Same here - Im using the same version as you and have had a ton of bug splat issues ALL day - its infuriating!

[Lysistrata Szapira]

4 hours ago, Faithless Babii said:

Same here - Im using the same version as you and have had a ton of bug splat issues ALL day - its infuriating!

Also same. I'm trying to open the group listing to look for group notices regarding a problem with a store's HUDs going immediately to a white screen where no colors can be changed. I'm also using the pre-PBR release of Firestorm.  Every time I open the group listing, SPLAT.  This just started today.  I'm heading over to the Firestorm forums, I guess. 

[MBeatrix]

6 hours ago, Lysistrata Szapira said:

Also same. I'm trying to open the group listing to look for group notices regarding a problem with a store's HUDs going immediately to a white screen where no colors can be changed. I'm also using the pre-PBR release of Firestorm.  Every time I open the group listing, SPLAT.  This just started today.  I'm heading over to the Firestorm forums, I guess. 

Yes, it happened to me with Firestorm 6.6.17. The only way to "fix" it was completely delete the viewer and reinstall it but the problem occurred again after a couple weeks.

I wonder if portions of that viewer version became somehow incompatible (besides voice) despite the Firestorm team says they are going to keep it available "forever".

[Xylinya]

I’ve had numerous crashes with Bugsplat error pop ups over the past 2 days - mostly on log in.  Have reinstalled Firestorm 6.6.17 as not yet tried the 7.1.9  update.  Have managed to stay logged in so far on viewer I reinstalled earlier today . 

[Jaylinbridges]

 Firestorm 6.6.17 was never bug free, far from it.  I would get infrequent bugsplats with it, seemingly random.  But FS no longer tracks bugs on  their last non-PBR viewer, so those that remain on 6.6.17 will have to tolerate the crashes. 

I have yet to have a bugsplat report on the latest FS alphas.  I also keep Mirrors turned off.

Bugsplats are created to assist FS programmers track down code and timing problems.  They are nothing new.  Bugs are forever!

 

Edited August 27 by Jaylinbridges

[MBeatrix]

16 minutes ago, Jaylinbridges said:

 Firestorm 6.6.17 was never bug free, far from it.  I would get infrequent bugsplats with it, seemingly random.  But FS no longer tracks bugs on  their last non-PBR viewer, so those that remain on 6.6.17 will have to tolerate the crashes. 

I have yet to have a bugsplat report on the latest FS alphas.  I also keep Mirrors turned off.

Bugsplats are created to assist FS programmers track down code and timing problems.  They are nothing new.  Bugs are forever!

 

That's right but these bugsplats are new. I've been using Firestorm 6.6.17 since it was launched, and these errors only started happening less than a month ago.

{EDIT] The whole thing (PBR) feels like Microsoft trying to force users moving to Windows 11. PBR Firestorm is the worst viewer ever, so bad that I even prefer 6.6.17 with all these new errors.

Edited August 27 by MBeatrix

[Jaylinbridges]

23 minutes ago, MBeatrix said:

That's right but these bugsplats are new. I've been using Firestorm 6.6.17 since it was launched, and these errors only started happening less than a month ago.

They do seem to run in streaks.  I was looking at my old crash logs for FS 6.6.17, and no crashes for a month, then a week of several, then nothing for weeks.  I think it depends on how and what you use your system also.  Only the FS developers would know if there is something in common for 6.6.17.   If I really stress my system, running multiple alts at busy clubs for hours, I will eventually either run out of memory, or get a sudden bugsplat crash.  Could just be a marginal memory cell that fails with temperature 10% of the time, when the system is swapping memory, etc.  It is system dependent, and software dependent (eg Mirrors).   

I also notice more general issues if my  avatar is inactive for many hours, such as sleeping in SL for 8 hrs.  Sometimes VRAM memory just fills up, and stays there.   I just relog to recover VRAM.  We used to call it memory leaks.  Haven't heard that term for awhile, since it was a Windows problem with older OS.  Now everyone has more system RAM, so nobody notices or cares.

 

Edited August 27 by Jaylinbridges

[Primrose Sorbet]

I am also having this issue and it's been going on for a couple of days now.      I cannot use the new version of Firestorm for various reason - so am having to stick with the previoius version.       I seem to crash primarily when I try and open my groups and don't have mirrors turned on at all.

[Maia Beltran]

This has also been happening to me lately - LOTS!  Immediately at the point of logging in and I am using FS 6.6.17. 

[MBeatrix]

2 hours ago, Primrose Sorbet said:

I am also having this issue and it's been going on for a couple of days now.      I cannot use the new version of Firestorm for various reason - so am having to stick with the previoius version.       I seem to crash primarily when I try and open my groups and don't have mirrors turned on at all.

Yes, that is exactly what I (and others) are experiencing. Every time I bring the groups list up, poof. Sometimes, even a group message makes it crash.

The Official Viewer runs fine (updated early today) but besides wandering around there isn't much I can do with it because of its limitations. Also, it's a PC killer — not possible to limit the FPS to less than 60 (enabling Vsync).

Edited August 27 by MBeatrix
typo

[Peroxide Bleac]

Having this issue too,  I can't really use the viewer anymore because of constant crashing, tp crash, tp crash etc.  I have sought help via Firestorm group in world, white listed in antivirus, complete clean reinstall of Firestorm 6.6.17 (70368).   I could try the pbr viewer with mirrors disabled I'm guessing?   but that sounds possibly worse! 

[Peroxide Bleac]

14 minutes ago, Maia Beltran said:

This has also been happening to me lately - LOTS!  Immediately at the point of logging in and I am using FS 6.6.17. 

Yes, this!  and it's happening repeatedly so not getting any quality time in world.

[Maia Beltran]

15 minutes ago, Peroxide Bleac said:

Yes, this!  and it's happening repeatedly so not getting any quality time in world.

And I should say, this only started happening recently. I have been using this version of FS for about 3 months or so. 

[Peroxide Bleac]

I just started using the official viewer out of sheer desperation but using it is not a substitute, I've never liked it.

[AmeliaJ08]

@Beq Janus

Just tagging you to be made aware of this thread, it's in the wrong subforum so might not be getting any attention. Seems lots of 6.6.17 (70368) users are getting bugsplat crashes recently, there's another thread on the Viewer subforum with similar reports.

[MBeatrix]

3 hours ago, Peroxide Bleac said:

[...] I could try the pbr viewer with mirrors disabled I'm guessing?   but that sounds possibly worse! 

Right, and it's not up-to-date, as the rendering subsystem has changed (it's why the Official Viewer was updated today).

[Aishagain]

Just a quick FYI.  While I wouldhope that LL would not introduce software mods that detect andhamstring non-PBR viewers, their apparently meek acceptance of the extended lifetime affords FS 6.6.17 users makes my paranoia bristle.

What I would suggest as a possible lifeline to those with more capable systems are the alpha PBR FS 7.1.9 versions currently being tested by some public-spirited/reckless individuals in SL.

I must emphasise that these are test viewers so just remember that and it IS expected that you report any anomalous behaviour if it arises.

They can only be accessed by joining the inworld Phoenix-Firestorm Preview Group but they are far more stable and gentler on less capable hardware (though you will have to turn off mirrors and reduce quality until you are satisfied.

There is no point in us railing against PBR, LL are determined to press ahead, despite their implementation via OpenGL being badly flawed, so we just need to find the appropriate band aids to our older less capable gear.

And Amelia is quite right, this is really the wrong thread for viewer-related issues.

Edited August 27 by Aishagain
Updated info

[MBeatrix]

1 hour ago, Aishagain said:

Just a quick FYI.  While I wouldhope that LL would not introduce software mods that detect andhamstring non-PBR viewers, their apparently meek acceptance of the extended lifetime affords FS 6.6.17 users makes my paranoia bristle.

What I would suggest as a possible lifeline to those with more capable systems are the alpha PBR FS 7.1.9 versions currently being tested by some public-spirited/reckless individuals in SL.

I must emphasise that these are test viewers so just remember that and it IS expected that you report any anomalous behaviour if it arises.

They can only be accessed by joining the inworld Phoenix-Firestorm Preview Group but they are far more stable and gentler on less capable hardware (though you will have to turn off mirrors and reduce quality until you are satisfied.

There is no point in us railing against PBR, LL are determined to press ahead, despite their implementation via OpenGL being badly flawed, so we just need to find the appropriate band aids to our older less capable gear.

And Amelia is quite right, this is really the wrong thread for viewer-related issues.

Yes, I agree that this is the wrong forum for viewer issues. But have you thought that the issue at hand may be caused by recent server changes?

PBR is fine, not my cup of tea as it is at this stage, but it's fine. I just would like to have the option of not using it sometimes. As I posted above, the Official Viewer runs fine, it's only a bit too limited for most of what I do in SL.

[Aishagain]

1 hour ago, MBeatrix said:

But have you thought that the issue at hand may be caused by recent server changes?

Yes, as I said I did and it makes my paranoia tingle!

2 hours ago, Aishagain said:

While I would hope that LL would not introduce software mods that detect and hamstring non-PBR viewers,

I also wondered if everyone suffering from maladies on reinstalled 6.6.17s did a true CLEAN instal, because in downgrading back to a non-PBR viewer that is VITAL

And redid ALL their whitelisting!

Edited August 27 by Aishagain
spelling: I kan't spel.

[MBeatrix]

29 minutes ago, Aishagain said:

Yes, as I said I did and it makes my paranoia tingle!

I also wondered if everyone suffering from maladies on reinstalled 6.6.17s did a true CLEAN instal, because in downgrading back to a non-PBR viewer that is VITAL

And redid ALL their whitelisting!

Yes, I always perform a clean install. I delete all cache and settings manually and clear all references to Firestorm from the Windows registry.

Today, I reinstalled Firestorm 6.6.17 once more (third time).

LL and the Firestorm team say they are keeping that version available "forever" but if things keep going as they presently are, thank you so much for nothing.

[Aishagain]

Well as a last Hurrah, I recommend you join the PFPreview group and try the latest alpha version.  It's only alpha because some of the updates are not fully released on the LL viewer (they weren't at the viewer release but they probably are now) and there are yet more tweaks and bugfixes (from LL and FS devs) being tested as I write this.

When PBR was unleashed on SL it was a shambles unless you had a fairly new and strong Windows PC, and we are surprised why?  That is par for the course with LL.  The good thing is that they ARE working hard on REAL fixes, because the FS useage graph showed them that they were in danger of throwing the baby out with the bathwater.

They just don't learn!  This is the introduction of Windlight all over again. And Yes, I WAS around then...I AM that old!

Edited August 28 by Aishagain

[KellyMorris]

8 hours ago, Aishagain said:

Well as a last Hurrah, I recommend you join the PFPreview group and try the latest alpha version.  It's only alpha because some of the updates are not fully released on the LL viewer (they weren't at the viewer release but they probably are now) and there are yet more tweaks and bugfixes (from LL and FS devs) being tested as I write this.

If you join PFPreview with a v6 they will not reply, it's only for v7, you should join normal group support. I doubt they will care of v6 anyway but i hope to wrong my feeling. 

Yes it's wrong to write it here but who can stay only on V6 have no place for having a help, LL v6 don't exist anymore, Firestorm not caring actually (maybe they will) Alchemy is only v7 (best viewer PBR). I fear v6 will end like Singularity, you can use it but wait 20 minutes before rezz the mesh.

I can stay with v7 but many friends no and not all can afford a new PC only for SL

Edited August 28 by KellyMorris