Worse, worse and even more worse with each version

I can not log in and when I can, I will get like one minute or less before MS Runtime detects a buffer overrun. Yeah and the technical "support" ... dunno if they ever read bugreports or crash-logs I send to them...

Lindens are so in luck that they are the only one having such a product on the market. No game, no office, no browser no what ever working that bad would survive long in the IT world.
Lindens, your software looks worse than Microsoft in the middle '90. Do you ever have had a thought about quality checking? I doubt so...

Edit: Just wanted to party this anniversary: 10th crash report now sended by the automatic crash reporter within 30 minutes! YEAH LINDENS RULEEZ!!!

Edit(2): Wow a new error: "Unable to connect. (done)" sic!

This is gonna sound stupid, but i was having that same problem.. I cleared my cache and was able to get right in...
Dunno if it will help, but it worked for me ..

Yeah that helped! I was able to be online 3 minutes now instead of 1 before crashin...

And it throw me out while "Precaching" now. So I do not even see the world starting to rezz...

Sorry, in vain as it seems...

I'm not crashing that often, I have actually had a relatively ghost prim free evening with hardly any problems.

How much Ram have you got? SL is a resource hungry bugger. Then there's graphic cards compatibility.

Yeah, I haven't had any viewer-side problems with either the latest regular viewer or the firstlook voice viewer.

1gb/256mb

Clearing the cache helps half the time. But it just delays the inevitable. Performance grinds to about 1 frame per 10 seconds.

Aaron, I agree with you to 100%. Up until version 1.14 everything was fine. I crashed now and then, but I could live with it.

Since 1.14 it's been all downhill. Mostly, it's a matter of minutes before I hang.

This happens both with Windows 2000 and Windows XP x64 Edition.

And yes: I have the latest drivers from ATI (Radeon X300), and I have disabled Vertex Shaders, Avatar Vertex Program, and VBO. Have tried the -noaudio flag too.

Does anybody at LL ever analyze those crash reports I keep sending??? This really SUCKS.

Mine doesnt not even have the reporter popup after a crash!. And i have mine turned on! Now tell me..........If the crash reporter is not working what makes us believe they are even reading the correct reports to start with.

They have a problem in the viewer when handling bad packets (yeah, an error in the error handler .. yay!), VWR-176

More prone to crashes when the grid is in bad shape and this one is particularly bad because it doesn't even let you send a crash report.

As of the day before yesterday I do have a direct comparison beween a Windows and a Linux client... Of course, it may be different with your setup (mine is Athlon64 3200+, 1GB, NVidia 7300, WinXP/Ubuntu), but I think I rather stay with the Linux client.

Same sim, same location, and around the same time - so that eliminates most of the variables. But I noticed that the Windows client is a bit more sluggish than the Linux client and it did crash two times in a row on me. Before that I _did_ notice (based on the performance meters) that the Windows client eats up the RAM faster than the Linux client does.

Feel free to try it out for yourself.

You wouldn't believe what difference running without leak would make:
http://nicholaz-beresford.blogspot.com/2007/06/tweaking-performance.html

Had a look. I'd like to see a diff of his client's source against the mainstream client source code before I give it a try. Can't be cautious enough...

The SL software has more bugs than a butterfly farm. Whats strange though is their ability to bork things that were fixed some 3 updates ago, which makes me think they are using the Jarrasic Park theory. You take good code and add 'filler code' to make up the sequence, without checking compatability.. and we know how that story ended.
The release of Open Souce for the client software was a cheap gain by LL to get talented unpaid enthusiasts to fix their dam code. Despite the hard work of those people, it is LL that are left to 'add the filler code', so what was fixed before, becomes unfixed again.
Anyone notice the IM window resizing itself again?? Open the IM window tab, resize it the window, open another IM tab, then close it and the whole window resizes back to default.

The last 12 hours or so have been particularly bad for me. I'm having the same problem as you, Aaron. I have 1 Gb RAM, and a 256k ATI Radeon X1600 graphics card. SL is chowing up my RAM at quite a pace. Usually before I login I have approx 78% of free RAM and a load of around 30% (as measured by FreeRAM XP Pro). Within about 5 minutes of logging in (sometimes less) I have 2% free RAM, and a load of around 80 - 90%. My SL bandwidth indicator also shoots up to about 5000 kbps, which is ridiculous. I am on a 1500 kbps download / 256 kbps upload broadband plan.

Try this:

http://www.secondlifeinsider.com/2007/06/14/leaks-still-leaking/

Or a direct link to the client they talk about (i.e. the one compiled by the person who fixed the memory leaks /not/ implemented last week by LL)

http://nicholaz-beresford.blogspot.com/

17d on my laptop didn't ever use more that 199,000 KB of ram after an hour (it started at roughly that amount and maintained it, give or take 1,000 KB).

They guy is a genius! All you fellow regressive luddites out there, I recommend this viewer. I don't know why it works better, and I really don't care. It jsut does.
/me applauds.

Updates are suppose to make quality improvements not these sort of problems we are consistantly having. Stabilize the grid PLEASE! Its great you want us to have sculpties and voice and more 3d enhanced realistic options but it doesn't even really matter all the new things if you lag so bad, and/or are bug riddled, that its pointless to move, build or try to enjoy the time most of us PAY for....LL wonders why they are overwhelmed by email??? IF YOU FIX THE ALREADY MESSED UP BUGS BEFORE ADDING TO THEM WITH NEW THINGS ...your emails of complaints, problems and general bitch'n would go down....this is something as a consumer I am very upset with because I DO PAY FOR MY MEMBERSHIP...and I have TOO many issues ....and I gave up sending in reports because as a person who has been in 3d worlds for longer then SL has been around, yes all my wares are updated....they all are running great....the lame reply of putting it back on me only further frustrates someone who knows a bit more then just pushing the power button. I just wish SL would FIX the issues before adding to them....we should look forward to update Wednesdays instead of all fear what will get screwed up next....

I think tomorrow I'm going to start using it for my alt-campers. See if they crash less often.

My viewer works just fine. I am not sure what everyone is bitching about. I use the Windows viewer and the Linux Alpha release. Both work great.
I think I prefer the Linux, but that is just a personal preference. Perhaps you guys have buggy, virused up computers.
My PC is clean and runs both viewers fine.
No--I don't work for SL.
Yes--I have used it since the Beta days 4 years ago.
Yes--sometimes LL goes backwards instead of forwards. IMHO the lag is and always has been the largest problem. Prims should be limited. Lag should be the number one priority.
Not sure what everyone else is complaining about. SL viewer simply does not crash on a regular basis. If it does for you than it must be your individual setup.

Well that is good news... a few systems run on the prolifercation of 'updates' without issue. My own systems are all top of the range high specified machines, before this last fiasco of an update, I could run 5 clients from one PC... but that was then, this is now. The issues are real... the people here are bitching real..

Preupdate I was getting FPS between 50-100+ depending where I was in SL, now I get between 5-45 since this 'new client', and you call that 'Yes--sometimes LL goes backwards instead of forwards.'? I would call that backward stride quite large, especially as they delayed by a week the rollout to 'tweak' the client before release. What were they 'tweaking', adding borked code so we would all feel at home?

The interesting thing is that with that last update, I did not see any changes in the source (I combed through all of them) that would account to that.

But there is a quite ironic detail about the memory leak, that is the memory is lost through network requests, meaning the better the grid runs, the more memory will leak (on laggy days, you simply have less net traffic, therefore less leaking).

I also found a leak (I doubt that it was introduced recently) which affects multiple instances of the viewer (just the 2nd to n-th) so with your 5 clients you'd defintiely run into that one too.


Nick

If you do the right (wrong) thing the viewer WILL crash. On a 512MB machine I can almost guarantee that I can crash the viewer within 15 minutes if I want t and on a 1GB machine it just takes a little longer.

It may be that your usage profile or RAM does keep you from crashing that often, but telling everybody who crashes it must be that their machiens are borked is definitely wrong.


Nick

Still not sure what to think about this issue. I asked some of my SL friends last night in world if they were experiencing crashes. To the last person the answer was "no."
I am not trying to flame anyone. I just don't understand. Clearly memory leaks are a concern, but as an example, on Sunday night I was in-world with three other people, all of them on Windows machines and me on a Linux box. We chatted for nearly 5 hours. Travelled around the world. Visited a party. Teleported. Rode a couple of rides. Rode a helicopter and a boat around. Played with some rezzing of prims. Looked at some art that we rezzed in and out. Never a single crash.
We all have 1Gig of memory or more. Perhaps that is the difference. We all have 256MB (or better) Nvidia graphix as well. Maybe it is our hardware.
Don't know. I simply have not experienced this "crashing viewer" syndrome.
Jay

Memory on the upside of 1GB definitely helps. It also helps if the grid is in good shape (as through the recent days) in regard to packet loss and inventory servers It also depends on what areas your are travelling, going shopping through many malls with many posters are worst ... outside areas or staying in one club for some time is less prone to crashing.

I'm not saying everybody is crashing all the time, it depends on memory and usage profile.


Nick