This 1.21 viewer crashes more! every 30 minutes

SL viewers have ALWAYS frozen for me, an hourglass starts up and nothing happens for 30 seconds, 1 minute... I have learned to accept it, annoying as it is.

But this RC has code that makes it CRASH if this happens? You put code in to make it crash?

Next time you do a RC viewer, can't you just make the viewer send a report and NOT bomb out?

If your goal is to not have crashes, and have the best functioning SL experience you can, you might want to use whatever version works best for you, be it the current RC or an older one, or the current Release viewer, or an older one, or an alternate client like Onrez or the Nicholaz viewer.

I am seeing a lot of crashes and they seem to be unrelated to my being frozen or even slowed down for any periods of time. I'll be mid-conversation with someone and suddenly be looking at my desktop. At other times, I am just walking along looking at things and CRASH.


Just here stating an observation pertaining to the Release Candidate Viewer since it seems that if I am going to use it then they want me to let them know if anythng acts oddly. So I am.

I've used it it all day, it's crashed a lot. If I were trying to build something or write scripts or conduct an event I would definitely not be using the release candidate viewer.

Indeed, this Release Candidate has extra code checking turned on for crashes. This means we sometimes cause the RC viewer to crash MORE often.
Read more about it in the Sticky post in this forum
/349/b1/279127/1.html

Same here, i usually like to use rc but this crashes at random points and especially looking at a sculptie will crash me.

Hi,

I have that with each interation of the RC viewer and think it is cuz LL activated the debug functionalities so that they can hunt more bugs down. So the RC will crash and send a crash log to LL where the official standard viewer would only issue a warning on the debug console. So I learnt to live with this increased crash rate in the RC, cuz normally it will be drop with each iteration and in the next official release it will be stable again If you do not want to beta test the RC, you better revert to the last stable viewer!!!

Regards Shyan

I think that this is the least stable RC yet,, hopefully we will all benifit from this, at least I can usually log back in with out having the 1 min (region is logging you out) or 5 min (you account will not be available until [timestamp])

Major, serious crashing here too with either RC or Stable release. Been already over a week and cannot continue building in SL.

Please try out RC2. We have turned off those extra debug checks now, so we think the crash rate of RC2 will go way down. It may still crash in places, and this is valuable to send us crash reports. But the stability of the remaining viewers should be improving now.

Thanks for your patience and willingness to help us test!

OK Ramzi, will do - I want to help. and can tolerate occasional crashes, I was complaining about how often.

Okay, the new RC2 solved the problem, am back to building now. Thanks!

I have had maybe 6 crashes in 6 months, now 8 crashes in 2 days. Always use the latest RC (forced), but pleaseeeee.

I think the problem is more than just some random crashes of the Viewer, but crashing the entire operating system and screwing up the file system as it goes down with it.

I think it has to do with big time memory leak, which had been reported in JIRA for so long, and it seemed nothing was done to address this problem. Memory leak will surely crash anything randomly. Unix is supposed to be the most stable operating system, and the RC Viewer can bring down unix entirely, causing kernel panic. The code must have corrupted the protected mode royally to cause such a system crash.

I don't care if it crashes the Viewer, but bring down the entire operating system is unforgivable.

Hi Folks,
Reading ur comments, I agree with much of what has been said! this latest update messed everything up for me where before everything worked great! Now I log in , during evening hours and with in 5 mins of log in I get logged out! With a message saying something is a matter with that region or my internet both have been checked! and are OK!

Now get told from live chat person that we can only use the 1.20.17 (98669) version if we wanna play SL what a bunch of crap ! past versions of the RC have worked better for me then the regular viewer hands down! lol

Will wait and see what new blundering things they come up with

Respectfully Steve57 Zenovka

No one is forced to use a Release Candidate viewer. You ARE required to use the latest RC, *if* you use an RC. The reasons for this have been explained. The RC is a test viewer. Unless everyone is using and commenting on the latest version, managing the feedback and using it to fix the problems becomes impossible.

You don't have to use 1.20.17. However, it plugs a serious security loophole. If you run earlier versions (which you can do, by using 1.18.5 with the Nicholaz patch, for example) you run the risk of someone being able to hack your computer and access your files.

How can i download an earlier version again ? I want to do that, but i'm also told that the new version was obligated now for security reasons.

One thing which is just annoying are these little professors telling us the obvious as it was rocket science.

Lindal, we know what we are doing here, we are telling Lindens the new RC viewer is crashing. I told it too on the proper thread, and the reason why I did it is that I'm testing the viewer by using it everyday, and I want Ramzi to know that it crashes more than any previous 1.21 RC version for me. He promised this to possibly be the last RC version, and no one wants (not Lindens nor us) the new official release to be an unreliable one.

So as long as no one of us is behaving like he doesn't know what an RC is, you can't pretend we shut up over the viewer crashing just because we could easily revert to the standard viewer. If all of us would revert to that in discouragement, this place would be even more sadly unresponsive than it is already.

By the way, I want to add to the previous posts that most of the time when the viewer crashes in the new, peculiar way of this RC5 version, then the crash log is not activated, at least not in any of my machines (all Windows, most XP). Increasing chrash rate and crash logs not being sent could give LL quite an unreliable information about this version's behaviour. This is very dangerous for its further development.

Mine does not crash, HOWEVER closing the viewer does not shut down the process for VISTA.

I have found that some applications on my computer will not load until I've gone into Task Manager, located and terminated "SecondLifeReviewCandidate.exe" from the list.

Worlds and textures definitely take longer to load with the current RC5

Then there's Snapshots, which can take quite a while to display the shot, even when an empty directory is set for saving.

We need a new sticky thread about ...client crash



Anyway, no crashings here

problems I am having with latest viewer:

extended periods of being a cloud - sometimes I never rez at all
clothing not appearing, attachments not attaching or detaching
extreme chat lag
crashing
teleporting to 0,0,0 upon clicking on a prim usually with a leg over my head and sometimes have to relog to get out
lengthy time to log in
generally very very slow and laggy

a new viewer has been released today

The new 1.21 client has some nice new features which I want, but I can't use it.

I am a builder and every time I want to change a texture it take 30 seconds or more to open the texture window. It is silly. The version 1.20 client only took about 5 seconds which was not great but usable.

It's unfortunate that this view has been released with NASTY SHOWSTOPPER bugs.

The viewer continuing to run after it quits is a HORRIBLE bug. Textures stalling (not loading) is another (which is, IMHO, the worst bug). Prim attachments vanishing when zooming in on a sitting Avi is a third. Compatibility with new nvidia drivers (clothes rendering incorrectly such as gloves making your entire torso white) is a fourth.

Come on LL - you can do better than this, and you HAVE done better than this. You just tossed this viewer out the door just to hit a date target. It's not ready. It shows that quality just doesn't matter. These may be hard bugs to squash, but they NEED to be fixed. This new viewer provides a bad user experience. It's a step backwards. Do the right thing, pull this viewer and get these bugs fixed first, and THEN release. This is a real black eye to the management team that made the release decision.