Whirly Fizzle

Please be sure to post the names of all your bots so everyone can ban them from their land. Thank you.

Are you using Norton antivirus? Norton is causing this problem over the last few days - see https://jira.secondlife.com/browse/BUG-11891 To fix: Uninstall Norton using the Norton Removal Tool at https://support.norton.com/sp/en/uk/home/current/solutions/kb20080710133834EN_EndUserProfile_en_us Note that just uninstalling Norton through Windows programs & features will not fix the problem, you must use the above removal tool. Then reinstall Norton & you should be fine.

Are you using Norton antivirus? Norton is causing this problem over the last few days - see https://jira.secondlife.com/browse/BUG-11891 To fix: Uninstall Norton using the Norton Removal Tool at https://support.norton.com/sp/en/uk/home/current/solutions/kb20080710133834EN_EndUserProfile_en_us Note that just uninstalling Norton through Windows programs & features will not fix the problem, you must use the above removal tool. Then reinstall Norton & you should be fine.

Are you using Norton antivirus? Norton is causing this problem over the last few days - see https://jira.secondlife.com/browse/BUG-11891 To fix: Uninstall Norton using the Norton Removal Tool at https://support.norton.com/sp/en/uk/home/current/solutions/kb20080710133834EN_EndUserProfile_en_us Note that just uninstalling Norton through Windows programs & features will not fix the problem, you must use the above removal tool. Then reinstall Norton & you should be fine.

Are you using the latest LL viewer release Second Life 4.0.4 (314579) Apr 26 2016 17:54:49 (Second Life Release) ? If so, there's a bug on that new viewer that breaks uploading snapshots to profile feed. See https://jira.secondlife.com/browse/BUG-11899 You can switch to a different viewer for now until the bug is fixed. The bug does not reproduce on the LL QuickGraphics viewer yet. but it will once that viewer is updated to include the default release changes. You can download the QuickGraphics RC viewer here: http://wiki.secondlife.com/wiki/Release_Notes/Second_Life_Release/4.0.4.314426

Prokofy Neva wrote: But all this brings me to a completely different issue back in SL -- whether I use Firefox or Opera (haven't tested with Crome) this odd thing keeps happening in SL and has happened now for I would say 9 or more months. While you're flying along, or sometimes just zooming around trying to do things from one sim, these browser windows just open up on you all of a sudden. Inword, a little browser window opens up and briefly retards your progress then closes. I don't get why that is happening or what it is. The view into the next sim? or? The window is small and black. It looks kind of like the CMD prompt window but it's inworld and just opens up. I thought at first it was related to media on a prim being somewhere, say, in a roadside ad. But that is definitely not it as I see it on sims where there isn't any media on a prim doing that, which in any event creates a window that looks different. Do you know what this is? Yep, there's a JIRA issue for that here: BUG-11349 - On CEF viewers, the console window that opens on top of the world view should be hidden. Singularity won't have this problem because it doesn't use CEF. Firestorm has the bug fixed: FIRE-17768 - A Dos window pops up every few minutes for a second. Workaround for LL viewer Disable media autoplay Preferences -> Sound & Media -> Untick "Allow media to autoplay". You'll still see the cmd window flashing up if you manually play some media though. You can totally disable media if you do not need it.

There have been big problems with that vendor for a long time. You likely wont get any help Further reading: http://www.sluniverse.com/php/vb/general-sl-discussion/115689-lab-chat-returns-will-ebbe.html.

Do you have RLV enabled? Make sure you are not under any active RLV restrictions that prevent you from activating a different group tag.

"You can't attach multiple objects to one spot" happens when you end up with a coalesced object in your Current Outfit folder.

That place is well known for constant spam teleports sent by bots. The bot accounts don't seem to remain active for very long. I guess they either get ban hammered quickly for spamming or the owners delete them because most people block after the first unwanted teleport. If you use Firestorm, you can block all teleport offers (or just TP offers from non-friends) when you don't have an active IM session with the TP sender. This will nicely block the Tramps TP spam. Top menu bar, Comm -> Online status -> Enable "Reject teleport offers & requests." Preferences -> Privacy -> Autoresponse 2 -> Automatic response to all avatars when in Reject Teleport Offers mode (spam them back ) Optional: Don't reject teleport offers (and send response) from people on friends list. Those options were added to Firestorm after many complaints about trhe TP spam being sent from Tramps.

Duplicate post: https://community.secondlife.com/t5/Technical/getting-bright-screen-then-booted-off/qaq-p/3027016

Hmm not sure why this isn't working for you. I'm still able to upload large images to my feed. The last image I uploaded to my feed was 2500x1591 pixels. I can't see your profile feed images because of your privacy settings. Which viewer are you using?

Yes, you can use viewer parameters to do that. Presuming you are on Windows, right click the desktop shortcut for Firestorm -> Properties -> Shortcut tab. In the "Target" text box, go to the end of the text, add a space & then add the text --graphicslevel 6 Apply -> Ok. Launching the viewer from this shortcut will always use Ultra graphics. Example: If your target path is: "C:\Program Files\Firestorm-Releasex64\Firestorm-bin.exe" Change this to: "C:\Program Files\Firestorm-Releasex64\Firestorm-bin.exe" --graphicslevel 6 Make another shortcut for Firestorm & this time use --graphicslevel 0 to launch the viewer with Low graphics setting.

Are you 100% sure that you have set the next owner permissions correctly on the scripts themselves?

Prokofy Neva wrote: Hi, no it didn't force a driver update, it's still that same one from Intel 4000, I checked with their driver update thing. Your driver HAS been updated - to a version without the memory leak so I'm actually hopeful the crashes will be gone now, even on the latest default release viewer. Before updating, your system info was: OS Version: Microsoft Windows 8 64-bit (Build 9200) Graphics Card: Intel® HD Graphics 4000 Windows Graphics Driver Version: 9.17.0010.2867 <---- driver release date: 10/10/2012 OpenGL Version: 4.0.0 - Build 9.17.10.2867 After the update to Windows 8.1: OS Version: Microsoft Windows 8.1 64-bit (Build 9600) Graphics Card: Intel® HD Graphics 4000 Windows Graphics Driver Version: 10.18.0010.4276 <---- driver release date: 21/09/2015 OpenGL Version: 4.0.0 - Build 10.18.10.4276 The graphics driver you have now is only one release behind the latest version and it should be just fine. Has the long hang when logging out also gone away? I suspect the driver update may have helped this too. When the viewer is logging out, it saves the screen_last.bmp (image of what's on screen when you quit the viewer) to disk & it also compresses & saves your updated inventory cache, Both of those things need free memory to complete, which you will have been short of when using that old leaky driver version.

Prokofy Neva wrote: Frankly, I'm finding it hard to believe that an upgrade to Windows 8.1 made graphics issues in SL subside but it may be an overall memory leak issue or who knows. Glad the crashes have stopped for now. I'm curious to know if the Windows 8.1 update also forced a driver update for your Intel graphics too. Can you go to Help -> About Second Life again & paste your system information to show the current driver version. I also had the same worry as Qie - the Occulus viewer is really outdated now. If you install the current release viewer from https://secondlife.com/support/downloads/ do the crashes come back? You can install the current release to a seperate folder so you can keep the Occulus viewer in use too. The Occulus viewer will be getting an update fairly soon & will be merged up with default release, so it's better to check the crashes are also fixed on default release now. If you do still crash on default release, if you can plop your zipped up logs folder onto Google drive or Dropbox or similar, I can take a look at your crashes.

Ok so you do have locked OEM drivers which can only be updated from Acer. If Acer hasn't updated their drivers for your system then yes, you are stuck without jumping through some hoops. The only way to know exactly why you are crashing on the LL viewer is to get your viewer logs. We need to know why you are crashing to help fix it. File a JIRA issue , run a session where you reproduce the crash and then before relaunching the viewer, zip up the logs folder & attach it to the JIRA issue using More Actions -> Attach files. To find your logs folder: Make sure hidden files & folders are set to show in Windows 8 - see https://kb.wisc.edu/page.php?id=27479 Browse to C:\Users\[uSERNAME]\AppData\Roaming\SecondLife Inside the SecondLife folder, you'll see a folder named Logs. Zip up the whole logs folder and attach it to your JIRA issue. One other guess what may be causing the crashes before seeing your logs - do you happen to be using Webroot antivirus software? Webroot isn't compatible with Http Pipelining used in the viewer & you will suffer frequent crashes. Singularity doesn't have the Http Pipelining feature & will not be affected.

What actually happens when the viewer crashes? Does the viewer just poof & close to desktop? Or do you get a message similar to "You have been disconnected from Second Life. View IM/Quit" ? This is a disconnect rather then a crash. Though a disconnect will happen if the viewer freezes for too long so is not always caused by connection issues. I can take a good guess at why you will be very crashy from your system information. You are using Windows 8 (OS Version: Microsoft Windows 8 64-bit (Build 9200)) rather then Windows 8.1. SL viewers are terribly unstable on Windows 8 compared to Windows 8.1 - the crash rate is pretty much doubled. First thing I would do is update to Windows 8.1 - see http://windows.microsoft.com/en-gb/windows-8/update-from-windows-8-tutorial You have Intel® HD 4000 graphics with driver version 9.17.0010.2867. This driver version is pretty out of date (from 2012!) & it's one of the Intel drivers that has a known memory leak - a severe one. If the viewer runs out of memory, it will crash. If that's the cause then updating your graphics driver will fix it. You can use the Intel Driver Update Utility to update your graphics driver: http://www.intel.com/p/en_US/support/detect or update the graphics driver directly from HERE.

This sounds like BUG-7761 where the attachment falls off serverside (so will be invisible to observers) but is still attached locally in the viewer. This bug is not yet fixed. The bug affects stacked attachments most often, so if you have any other attachment attached to the same attachment point as the mesh body, move it onto a different attachment point. This may help reduce the frequency with which the bug happens but it won't totally fix it.

Enable the Advanced menu in the top menu bar with CTRL+ALT+D Then Advanced -> Highlighting & Visibility -> Hide selected -> Make sure this is unticked Does this fix your problem?

The win_crash_logger process failing to shut down when the viewer logs out, or being very slow to shut down, leaving orphaned processes, which can eat a lot of CPU is a known issue (BUG-11795) & is being worked on. Until this problem is fixed, when you logout of the viewer, kill the win_crash_logger.exe process if it's still running before you login again.

You can't use that font ( Ω Ω ). If you set that display name using Firestorm legacy profile, the display name will revert. If you set that display name using your web profile, the name will change to Korean characters - see https://jira.secondlife.com/browse/BUG-11555

Are you located in Egypt? If so, see https://jira.secondlife.com/browse/BUG-10532

It's from Little Bones .

Arwen Serpente wrote: Whirly Fizzle wrote: Arwen Serpente wrote: - For some reason, the "beta" website only shows 585 of my products when I use the "my store" drop down from "My Marketplace", or "visit this store" from a listing. This may or may not have anything to do with the beta search engine, but it's rather annoying to have 588 products listed and active, and have 3 go missing in the Beta. Where are they? This is happening to a lot of stores, though not all. I filed a bug report for that here: BUG-10769 - [sLM Beta Search] Some store pages have missing listings when using beta search This glitch - the beta showing a different number of items in a store vs. the actual store on the current MP - still exists, hasn't changed. I went to comment on the JIRA, but it is closed as "unactionable". Any ideas what we are supposed to do, or, is it really going to be left unsolved? p.s. Whirly, I'm replying to your post because you had replied to mine way back in Nov 2105, trying to keep the subject organized. The comment is really directed at the LL team coding the beta. Best thing to do is to file a new JIRA issue about the missing store items when using beta search.