Whirly Fizzle

Ok, I suspected it wouldn't. Get that support ticket filed with LL support. In addition - if you want me to take a look at your viewer logs (I'm Firestorm viewer support), then file support issue with Firestorm too (see http://wiki.phoenixviewer.com/file_a_jira ) & I'll take a look. Please reference this forum thread if you file a Firestorm issue so I know who you are. Your logs will likely give a good clue to what's causing the problem but if it is an inventory issue, LL support are the ones that will fix you.

It's one of those difficult situations because explaining how this works pretty much tells someone how to work around that ban.

Clearing cache before each session may or may not help. It depends what's causing the problem. Clearing cache is likely to only work if your problem is caused by inventory views taking too long to create during login and causing your login to take too long and time out. Your case doesn't sound like this - it sounds like the viewer is locking up & going not responding when inventory is trying to fetch after you get logged in. Anyway, It's not going to hurt to try a cache clear to see if it helps. Even if it does help, it is only a workaround & you need to get the underlying problem fixed. To clear your cache: Launch the viewer to the login screen. Firestorm: In the top menu bar of the viewer, go to Viewer -> Preferences -> Network & Files -> Directories -> Click the "Clear cache" button -> Apply -> OK. LL viewer: In the top menu bar of the viewer, go to Me -> Preferences -> Advanced -> Click the "Clear Cache" button -> OK. Restart the viewer and login. If this does work & you can get logged in & remain stable you will likely have to clear cache before every single session until you get the cause of the problem fixed. Best thing to do is to file a support ticket with LL support here: https://support.secondlife.com/create-case/ Choose "Technical Questions" -> "Inventory (un-rezzed) issues. Be sure to make it clear that this problem only affects one of your accounts. tell them you suspect it's an inventory problem and ask for your inventory structure to be checked.

MelissaSchonkeren wrote: But is there any official documentation of this implementation tho? No...

Jelli Kohime wrote: Because I kinda need Imprudence for some things I do and I don't think any other viewer has the weird feature I need. What feature is that?

I can only guess without seeing your logs. You already confirmed the problem happens on all viewers. Next important question - does the same problem happen with your alt accounts? If this only happens with one of your accounts, it's likely to be an inventory issue - crazy number of duplicated calling cards updating online status at login can cause a freeze like this, or an inventory folder with many many thousands of items in it or some other kind of inventory "corruption". It may also be caused by something the affected account is wearing. If this does turn out to be account specific, best thing to do is file a support ticket with LL and ask for your inventory to be checked. Support can fix these kinds of inventory problems.

Leading spaces in group names are supposed to get stripped out, however it seems buggy & not all group names with leading spaces have been "fixed". See https://jira.secondlife.com/browse/BUG-11303 LL do sometimes make changes to group names at the founders request however there has to be a very good reason for them to do it. We had some of our official support group names changed when Phoenix viewer was replaced with Firestorm viewer.

If your Webroot subscription has run out then as Oz said, I'd advise you to choose a different antivirus software. Webroot really is the most problematic antivirus out of all of them with SL viewers. If you have already uninstalled Webroot, you may still see seeing corrupted textures or mesh if they were fetched & cached with Pipelining enabled. Clear your viewer cache once and everything will be back to normal. If you decide to keep using Webroot then you can work around the problem by disabling Pipelining in the viewer. Activate the Advanced menu in the top menu bar with CTRL+ALT+D Advanced -> Show Debug Settings -> HttpPipelining -> Set this to FALSE. I would actually do this from the login screen because you will likely crash when logged in & the settings change will revert. From the login screen, it's Debug -> Show Debug Settings -> HttpPipelining -> Set this to FALSE. You then MUST purge viewer cache because it will be full of corrupted textures that you fetched with Pipelining. You only need to purge cache once after changing the Pipelining setting. For Firestorm from the login screen: Viewer -> Preferences -> Network & Files -> Directories -> Clear Cache -> Apply -> OK. For LL viewer from the login screen: Me -> Preferences -> Advanced -> Clear Cache -> OK. Restart the viewer & everything should be back to normal. For details about the Webroot problem: LL JIRA: https://jira.secondlife.com/browse/BUG-11314 - Graphical Errors - Webroot + Pipelining incompatibility Firestorm JIRA: http://jira.phoenixviewer.com/browse/FIRE-17661 - HttpPipelining - Webroot Crash with fault error ntdll.dll mesh fails to render, texture corruption Hope that helps.

Are you using Webroot antivirus software? The corrupted textures shown in your image plus a swift viewer crash (especially on a clean cache) match the symptoms of having something installed on your system thats barfing all over Pipelining in the viewer. If this is the problem then ultimately, Webroot (or whichever antivirus/Firewall software you are using) need to fix their bug . You can work around the problem by disabling Pipelining in the viewer. Activate the Advanced menu in the top menu bar with CTRL+ALT+D Advanced -> Show Debug Settings -> HttpPipelining -> Set this to FALSE. I would actually do this from the login screen because you will likely crash when logged in & the settings change will revert. From the login screen, it's Debug -> Show Debug Settings -> HttpPipelining -> Set this to FALSE. You then MUST purge viewer cache because it will be full of corrupted textures that you fetched with Pipelining. You only need to purge cache once after changing the Pipelining setting. For Firestorm from the login screen: Viewer -> Preferences -> Network & Files -> Directories -> Clear Cache -> Apply -> OK. Restart the viewer & everything should be back to normal. For details about the Webroot problem: LL JIRA: https://jira.secondlife.com/browse/BUG-11314 - Graphical Errors - Webroot + Pipelining incompatibility Firestorm JIRA: http://jira.phoenixviewer.com/browse/FIRE-17661 - HttpPipelining - Webroot Crash with fault error ntdll.dll mesh fails to render, texture corruption Hope that helps.

AlexanderD, I suspect you have this bug: https://jira.secondlife.com/browse/BUG-11265 There is a fix for this bug in the latest Maint-RC viewer. You can download it here: http://wiki.secondlife.com/wiki/Release_Notes/Second_Life_Release/4.0.2.311378 There's a couple of pretty nasty bugs in this viewer - no hover text will display on worn attachments and the viewer will not render ban lines & if you atemmpt to cross into a banned parcel the viewer will crash. There will likely be an update soon to fix those 2 bugs, but give it a try & see if it has working profiles & search.

Is your password over 16 characters in length? When you change SL password it used to (maybe still does?) allow you to use >16 characters quite happily. V3 based SL viewers silently discard password characters after the 16th. Other places where you login to your account on the web pages don't do this. This can lead to your password being accepted in some places and not others. The same problem can happen if your password uses special characters. If you password is over 16 characters or contains special characters, try changing assword & try again. If that doesn't help, best thing to do is to file a support ticket

Gabi, are you using Webroot antivirus? If not, which antivirus & firewall software are you using? I suspect you have something installed on your system which isn't compatible with Pipelining in the viewer - this will lead to lots of corrupted rainbow textures and exploding mesh & frequesnt viewer crashes when a lot of uncached content is about.

Can only guess without seeing your logs, which will show at what stage of the viewer shut down process the hang occurs. Do you get the same logout hang on your alts? If it's account specific it's likely to be a stall updating & compressing your inventory cache. Possibly a very large & flat inventory? If all accounts have the same problem, are you low on hard drive space on the drive you use for cache? Sometimes the viewer can hang forever when shutting down the mesh repository or when shutting down the audo engine. This should be a very very occasional thing though - I see it a couple of times a month at most & it can happen on Firestorm or LL viewer. If you have a mesh upload attempt hang on calculating weights & fees & you cancel it, the viewer then has a fairly high chance of hanging when shutting down the mesh repository. If you have the problem on all accounts but the problem is more severe on accounts with large inventories and the problem only happens on one viewer build and you also have longer login times then normal & the viewer freezes badly (10-20 seconds) each time you open AND close the inventory floater & the viewer uses way more memory then is normal then those specific symptoms usually mean Windows is running the viewer in some hidden "debug" mode (usually fault tollerant heap) and this can happen after a nasty heap type crash. It's rare but it happens. This can be fixed by removal of the offending registry key. Quickest way to find out where the hang is happening is to file that Firestorm JIRA & attach your logs.

Each time you clear viewer cache a new calling card will be created for every friend: https://jira.secondlife.com/browse/BUG-10703 There's a fix for that in the LL Maint-RC viewer. Also fixed ready for the next Firestorm release.

You can bring up the Develop menu on both viewers with CTRL+ALT+Q. Advanced menu can be activated with CTRL+ALT+D.

I wanted to ask the usual suspects on the Deploy Thread if we could possibly be spared their weekly whining sessions for every single grid roll about how inconvenient it was for them. Instead I was adult & used the block button :matte-motes-zipped:

The reason for the emergency roll: https://community.secondlife.com/t5/Tools-and-Technology/Why-the-Friday-Grid-Roll/ba-p/3006809

Sounds like we will get a post-mortem once all regions have rolled: http://modemworld.me/2016/02/19/sl-project-updates-16-72-unscheduled-server-deployments-sl-viewer/ Speaking at the Server Beta User Group meeting following the deployment, Steven Linden had this to say: We had an unscheduled RC deploy earlier today. It’s for a security vulnerability that was released, and we discovered that Second Life regions were vulnerable. A full public post-mortem will be coming after we deploy to the rest of the main grid. I can’t say until it goes out to the rest of Agni; I can say that it was related to region availability only…. I honestly can’t say a great deal, other than we have a fix, and that it’s coming very soon to the rest of Agni.

Without more info I can only take a very wild guess. Seeing as this comes up a lot, I'll take it. Does your system have Intel graphics & are you using a really old graphics driver? A batch of older Intel HD graphics drivers had a severe memory leak which can cause you to crash very easily when you move your camera or avatar or any new textures enter the scene. Updating your graphics driver will fix that. Second wild guess - do you happen to be using Webroot antivirus software? If neither of the above apply, can you describe in more detail what happens when the viewer crashes? Does it: * Silently crash to desktop -poof! * Lock up & go not responding for so long that you get disconnected. * Do you see a message saying "You have been disconnected from Second Life. View IM/Quit"? Can you go to Help -> About Second Life, click the "Copy to clipboard" button & paste all your system info in a comment.

I would choose either Account Issue -> Second Life Viewer Login Issues, or Technical Questions -> Inventory (un-rezzed) Issues. As long as you explain you need a sync to Aditi under the "Please describe the issue" section, it should be fine. Support will shuffle it to the correct place.

If you mean that you moved in RL, then you can change your contact address here: https://secondlife.com/my/account/contact.php?lang=en-US

Not frustrating at all so don't worry Those extra exposed settings for shadows & Ambient occlusion you will find under World -> Photo & Video -> Phototools on Firestorm. Word of warning though - some of those exposed settings are "dangerous" in that they will crucify your performance if you push them too high for your system. Be especially careful with the Shadow Resolution (Shd. Res) setting. If your system can handle it, you can crank it up BUT if you try to take a very large sized snapshot with Shadow Resolution above 2.0, you have a good chance of crashing the graphics driver, even on a Titan card or a GTX 980. The D button next to all those settings will reset to default. You may find this tutorial helpful for learning what all these shadow & Ambient Occlusion settings do in Phototools:

Hmmm that wobbly effect is normal. You'll even see that on the default avatar mesh & shadows cast on objects. You can lessen the effect by tweaking the shadow settings. Im using Firestorm for these images but the effect is just same on the LL viewer. My avatar is wearing no mesh on its upper body here. Sun is set to midday. The shadow in the chest is cast by the avatar head. Close up image showing graphics settings. Shadow and ambient occlusion settings are at defaults.  Here is a gif showing how flickery the shadow is when moving camera. https://i.gyazo.com/ee9da0e66f5b17d41ac01735944b90fb.gif If I make these changes to shadow settings it mostly eliminates the problem:  Here's a gif showing the shadows with the above settings while moving the camera: https://i.gyazo.com/dc4d9dc031c531d0de1c184c786593ee.gif Cranking the shadows or AO settings up like this do have a performance penalty. Curious if you remove the hair from the mesh head shown on your video if the flickery shadow near the eye goes away? Is there a transparent mesh layer in that area which could be making the effect worse in that area? Possibly a problem with inverted normals in the areas that flicker badly on that head?

Guys, be aware that enabling TextureLoadFullRes will cause you to crash all the time from out of memory & will also cause you extreme performance problems. You'll also see a lot of broken textures. Even a top gaming system will suffer with that setting enabled. It isn't a fix.

Login to https://my.secondlife.com/ in a web browser. Go to https://my.secondlife.com/Jess3746 Settings -> Privacy -> Feed Make sure Feed is not set to "Nobody". Having feed set to Nobody may well block access for yourself too. Edit to add: When you bring up your profile inworld in the viewer, do you see a padlock icon with resticted profile content including your Feed missing? This is a bug in the viewer since CEF. Click the padlock button and login & make sure remember on this computer is ticked. See if you can then see your Feed images.