SL client memory leaks very extreme

I switch between latest release version and windlights all the time and see the same issue in both. After running for a couple hours sometimes less, the client get's real stuttery and then the inevitable out of memory in the old client or in windlight a nice crash.

I am running vista 64, with 4gb ram, 8800gtx, etc... memory is not an issue for me. I know that whoever makes SL client is obviously not freeing memory up on the client somewhere, but does anyone else besides me get the issue or am i only one who can stay connected long enough to get the issue?

some notes
1) i teleport around ALOT
2) happens after visiting alot of SIMs. which is really not much time for me. So i doubr someone who doesnt port around alot would notice it as fast.

I had/have the same or similar problem of stuttering badly after loading everything up, I toyed with different viewers and graphics options and nothing. I could survive for a while but it'd jus get slower and slower until I get a black screen and I have to manually turn pc off which is a pain.


I set my graphics options to mid and everything seems to be ok so far with the new viewer.

The memory leak issue has been around for a long time. The nicholaz viewer (search in these forums for links to his website to download it) fixes a lot of the problem apparently.

EDIT I don't know much about it, but I think a lot of people have commented that SL doesn't like Vista 64, although it runs fine on the 32-bit version for me.

After looking a bit more into it I don't think it's /really/ a memory leak perse... (that being "lost" memory) but rather just painfully slow deallocation of resources to the point that memory is not freed fast enough. Not that I've bothered to actually try to debug it for real...

It looks like LL may be using some kind of "Garbage Collected" memory mamagement library. What I've been seeing is that ememory use will get up to about 1.4 gig, the suddenly ALL AT ONCE the GC will kick in and free up 600 Meg of ram stalling the client for like 15 seconds.

This is pretty typical of GC systems, they pretty much ALL suck for handling huge amounts of allocations/dealloocations and of large objects and SL has both in SPADES.

I think that the only real hope is that the client get away from the current GC system for large allocations (textures most likely the biggest culprit) and write their own specialized memory handler to free textures ASAP or at least SMOOTHLY release them when unnneded and not 600 meg of them at once :/

I'm guessing your problem is the 8800s. I have a dual-8800 system and it can run the regular client for about 30 minutes on a good day and Windlight for about 15 minutes before they crash.

My system with the 7950 can run the client for hours.

Pay more, get less.

Trolane, I downloaded the lastest viewer yesterday (Id had dazzle previously, with no problems).
The instant I got inworld the screen freezing business started, everytime I tried to move myself or the cam...freeze....then it would go a bit, then freeze and ultimately black screen with the (not responding) at the top left of the window.
I have a good nvidia card and the dazzle viewer was good.
I then tried the new viewer with the windlight incorporated...same problem, constant freezing....
So I went back to the dazzle viewer and bingo...it was noticably better immedately.

What concerns me is if/when they incorporate dazzle into the main viewer that I will have to put up with this constant freezing which makes it so unpleasant to be inworld that I rarely do anything but sit in one place.

I wish I could report this somewhere...the Jira site seems set up for specific problems and Ive already voted on one report about screen freezing but...what is it that dazzle doesnt have that the others do that causes the freeze, how is there a way I can report this?

I have a memory leak also that I can watch fill my physical memory in my Task Manager.
The new release makes it worse so i assume there is now many leaks contributing

nuff said, nearly 8 hours and SL runs out of memory and its just using up to 32bit limit 'course ,then it crash, give this client a largeadressaware allready .

No this wouldnt make it true 64bit client, but it would allow it to use ram without hitting 32bit limit then skydive crash.

Yeah I got the same issue and have noticed it for awhile.
Since the latest 1.19x versions I've now got about 2 hours until I get a memory issue.
And running photoshop side by side? Forget it. Maybe an hour tops.
PH CS3 has it's own type of memory leak.
Apparently it can't close out certain files correctly.