This new viewer sucks all my memory

slurp slurp!

looks we got a leaky client...

anyone else have the same problem or any solutions?

Yep, and it is being addressed in Jira also.

me thinks there is a huge memory leak or something dunno but my puter wants to blow up half the time

So yesterday I was DJing, noticed a sudden drop in performance. Hit the task manager and noted that SL was eating 843MB of my Memory.


SAM was using about 28.

I have 1024MB or so available. So please fix it.

Mine too!

Is this going to be fixed, do you think, or is it just another thing we have to live with?

coco

I also have 1 gig of memory and currently sl is using 755MB!! what on earth is it doing with all this ram??

Same problems here. Computer with 2Gig of RAM. I have to reboot my computer every 45 minits or it will crash.

Well, at least its not just me...

That really doens't make me feel any better.

I got one of those little ram clearing utilities and it goes off every ten minutes...sheesh.
That seems to help a little.

It's not just you and it's been doing it since the 1.4 beta (or first look client).

Dozens if not hundreds of bug reports filed and "addressed on Jira" == nothing at all has been done.

This has been a MAJOR pain and responsible for the "frame rate drops to single digits while turning" problems for WEEKS.

A fine example of a very large, severe bug being all but ignored by LL while they fix little UI glitches and play with the keyboard focus again. (and of course add world dividing features like "voluntary" age verification and voice chat) This is what happens when you let the coders decide what they /want/ to work on instead of having a proper system that tells the coders what they HAVE to work on, the REAL problems (the /hard/ problems) go virtually unaddressed.

Another new and highly annoying bug is the spurious flashing of particles in a very large number of particle scripts in 1.5. A long standing bug that for some reason on 1.5 has gone insane. How long before that is fixed?

LL seems to not subscribe to the /proper/ policy that bugs introduced in an update should be the very first ones squashed in the next update. This is how you prevent a completely out of control bug list as we have right now. Bugs are EASIEST to fix immediately after they are introduced, and most importantly, newly introduced bugs are the /worst/ bugs as far as the users are concerned and the faster you fix those the better on the users frazzled nerves.

I still don't think there is a single serious engineering manager at LL. 69% of an engineering staff working on bugs and efficiencies is insane. This should 10-15% tops. If SL was not so utterly broken by the nut house development process they have in place it would not be necessary to utilize 2/3 of your workforce on "fixing it later".

Does the same for me. 1.5 seems a little better. 1.4 was unusable. After about 30 min the mem and cache load up and I have to relog. Guess we have to live with it or go back to Warcraft.

It's all those TV news crews skulking about the grid.

yeah 1.4 i could not even use at least i can semi function I still can't play properly though and I really dont know what to do ad more ram? will it just fill it up in 5 minutes more? (this is not the answer) . Get a super duper delux 8100 nvidia ultra cool 90000 buck graphics card? (dont think that helps either Oo) so meh

I just opened up a subscription to a few mmorpgs in case I get borred cause honestly I have to stay off of second life lest I throw my computer out the window right now. I play an hour at most a day if that. LOng enough to upload a texture or two and work on some project bring it a few steps closer to completion but its taking me 2 weeks to build a small building because I get tired of crashing

Its almost done now but usually i can build a building minus final tweeking in an evening

Maybe they should stop using Mozilla!!

But Philip's STAFF is HAPPY. That's the most important thing.

coo

Everything is going swimmingly then my computer starts babbling like a meth head on a three day tear--it goes on and on and on until I just want to slap some sense into it--can't do anything but leave the room in disgust.


Is that what you mean?

This problem has been much more frequent and pronounced since the last update...

I have 2 Gigs of RAM and checking usage after a couple hours shows nearly 1.5G in use by SL. Yes it's a leak and it's been like this for me the last 2 clients - though worse in this one for sure, at least for me.

Oh and Caldonia, that cracked me up

Not sure this will apply to others but I think I have found a temporary way to reduce the memory usage at least to stop it to immediately crashing my pc letting me saving any unsaved work.

I keep an eye on the memory usage and when it gets too high I just minimise the screen and the memory usage will immediately drop. After maximizing, the memory usage will then again build up but it gives me some time to finish any outstanding jobs.

And don't flame me if this does not work for you or if it has been mentioned before!