December bugsplats
Robin Shadow
This was not only happening on Firestorm viewer 6.6.17, BUT also isues on SL viewer. Touching any group to change, or trying to use landmarks on notecards: All December, both myself and my wife (on separate pc's) were having the same issues. Any time we would go to use a landmark on a notecard, (whether I made the notecard, or it was also happening with the Hop Around Event notecard) or touch a group to change during advent, we would both bugsplat. Once a bugsplat occurred, we could not log back in for hours and sometimes not until the next day. We would both try the sl viewer, and could not log in there, same goes with the mobile viewer, so it was obviously an sl side issue otherwise why could we not log in on any viewer? When I could not login because of the bugsplat, my wife tried to log me in on her pc and she could not accomplish it there. I also tried her account on my pc when she was unable to login, same result on my pc. It was NOT an internet issue as she was still online when I was unable to login, and vice versa. Rocky Linden in support tried to help. Neither he nor Freckle Linden could find anything wrong with my account or my inventory. Rocky closed my support ticket and suggested I write everything here. The support Ticket was #2446401, you can find all the times I was bugsplatting listed there and the attempts to rectify the issues. During all this, I tried changing to a system avatar, no fix. I uninstalled viewers, reinstalled them, no fix. I cleared all caches, no fix. I have had many more problems than these ever since I started this account. I really think part of it may be the server my account is in as my wife has not had many troubles at all in comparison. The last bugsplat I had was on New years eve. I have been afraid to change groups or use landmarks since. I found an interesting notice on the sl viewer. It states that login and intermediate inventory issues were resolved on Dec 6th. That is right around the same time we both began having this recurring problem with group activations and landmark bugsplatting issues.
Below are 2 gyazo pictures of the error messages I was receiving on sl viewer when I could not log back in as well as the dec 6th message for reference.
Log In
Hecklezz Resident
All of their bugsplats on Firestorms side since Xmas is nvoglv64 related crashes where the callstack is completely devoid of any useful information, and doesn't at any point in the callstack point back to a place inside the viewer.
Also regarding not being able to login, the solution 90% of the time is to simply log into a different region than the one you crashed in (so don't use last location or home).
Dan Linden
Hi Robin.
I don't see any Second Life viewer bugsplats from you or your wife. We don't receive bugsplats from the Firestorm viewer. You might consider reaching out to the Firestorm team about the FireStorm bugsplats - https://wiki.firestormviewer.org/file_a_jira
These symptoms remind me of a router I had. The next time this issue happens, try restarting you router and see if that allows you to log in again. If not, restart the modem or any other network equipment in the path to the internet and try logging in again.
If restarting hardware does not resolve the issue, please quit Second Life, and then zip up your viewer logs folder. This page tells you where to find the logs folder: https://community.secondlife.com/knowledgebase/english/how-to-report-a-bug-r224/
Next, email the zip file to bug-attachments@lindenlab.com and reference this issue name in the email subject line.
Leave a comment on this canny issue once that's done so we can take a look at the logs.
Thank you!
Robin Shadow
Dan Linden
Hi, thank you for responding. The bugsplats were not happening on the sl viewer, but on the firestorm viewer 6.6.17. (final pre-pbr viewer) Firestorm is doing nothing about that viewer at this point to my knowledge. However, once bugsplatted, neither me, nor my wife could log back in using SL Viewer, (as the gyazo photos above showed the results) Firestorm Viewer, or SL Mobile. If it were simply a firestorm issue, why could we not login at all for hours or up to a day on any viewer? That sounds to me like an account glitch or an sl server issue not allowing logins on any viewer. (I coiuld be wrong, but that is what it sounds like to me) I do have a question, if my wife was logged into SL on her pc, and I bugsplatted, and could not log in again for hours, with us both using the SAME router, how could it have been a router issue? (however, that does not account for sl mobile being on 5g or 4g and no login there either.) My wife was still online, while she was logged in, she tried logging me in on her pc after I would bugsplat, and could not. Please believe me when I say I am not making light of what you said, merely asking a question. That scenario happened quite frequently in December. Both of us however, would bugsplat from changing groups, (we would not even be able to click to change, merely touch the group name and splat) or trying to use landmarks on notecards. My wife figured out she could use teleport history, and she would not bugsplat, but I would be locked out for hours at a time. Just adding info that may help sort this out. This issue has not happened since the December advent ended Thankfully, so I am unsure if it has been fixed or not, but I will say this, I DID try in the recent past to contact firestorm about an issue and was told "if you don't like it, write your own viewer" (their exact reply) so I kind of doubt I would have luck there. If it happens again, I will definitely send logs. I hope this makes some sense to you.
Hecklezz Resident
Robin Shadow I don't know who on the Firestorm side would have said that or if it was even a team member of Firestorm (if you asked in the Firestorm support group chat it could have been someone completely random who answered you, not from the Firestorm team as anyone can answer there), but if you check our Jira, myself and other developers are constantly helping fix bugs and answer questions, and there is also many support questions that come in (that only the person putting in support requests can see) that get their questions answered swiftly.
If you had put in a Jira ticket about not being able to login, we could have provided you the answer instantly, which is to login into a different region besides the one you crashed in that isn't last location or home (works in 90%+ of cases where logins fail after a crash). If you need an example to try, do- Cyclops
As to your bugsplats, unless you haven't been submitting most of them, all your bugsplats since Xmas point to nvoglv64 which is Nvidia's opengl code, not the viewer. If you haven't been submitting most of your bugsplats, what you describe happening regarding groups and landmarks and what not, sounds like the very old 6.6.17 crash that we can't go back and fix that occurs because of 2k textures being used on groups profiles and region land profiles. Using any PBR viewer will fix that specific bugsplat if it is what I suspect it to be.
For your bugsplats occurring before Xmas you submitted, I do see that they are all the LLImageGL::analyzeAlpha(2165) crash which is exactly what I just mentioned above and is the 6.6.17 crash regarding 2K textures we cannot fix for that version, you need to use an updated viewer.
Robin Shadow
Hecklezz Resident thank you for the reply. I remember I had asked a question in a technical section of a firestorm page, and that was the reply I received. I don't remember who posted it, but I do remember the reply. It's OK. I had been advised to login to pooley, and that worked but again as soon as I or my wife would try to touch a landmark on a notecard, we would bugsplat again. Same goes with groups. Click chat, groups, and splat. Would not even have to touch a specific group at times, other times it would splat as soon as a group name was touched. I always click to send bugsplat data because I know it helps fix issues. As for the pbr viewer, I wish we could use it. We have tried. It overheats our video cards and really lags sl out. Before you mention that there are many sites showing how to minimize the lag and make it run better, we have really tried for days and longer, and where we used to get 40 to 60fps on 6.6.17, we can not get above 15fps on any of the newer viewers. It sucks especially now with the major electronics price hike, it will make it almost impossible to upgrade pc's.
Hecklezz Resident
Robin Shadow Regarding being unable to use PBR viewers, that is unfortunate. Because the crashes you are having regarding groups and landmarks were fixed years ago since 6.6.17. There is literally no way to stop those bugsplats from happening without updating. With more and more people using 2k textures on their profiles, groups and land profiles, the bugsplats will continue to grow as I'm sure you have noticed.
Robin Shadow
Hecklezz Resident thank you for the info, I do have to ask, when we were not even opening the groups, but only clicking their name, how would a 2k texture be involved? Also, when all we were doing was clicking a landmark linked on a notecard, how would the same be involved to cause what we were experiencing? No pictures were there to come into view in either case. I am not discounting your explanation, but simply making sure we are on the same page.
Hecklezz Resident
Robin Shadow because the 2K texture is still being fetched and processed right as you click on the group or landmark in the notecard, so it is ready if it needs to show it. Your bugsplats that aren't the nvoglv64 crashes, (LLImageGL::analyzeAlpha(2165) or (2175)) match the known crash for the 6.6.17 2K texture crash I'm taking about, so it is 100% that.
If you know the group or land owner of the groups and lands that have a problem, try contact them and ask them to reupload the images as 1k if they wouldn't mind, and that should resolve the crash.