Welcome to the Second Life Forums Archive

These forums are CLOSED. Please visit the new forums HERE

Memory, how much do u use?

Mika Koltai
Registered User
Join date: 4 Feb 2007
Posts: 18
04-11-2007 02:02
I´ve logged in for some time now and it´s getting laggy and jumpy, so to say crappy. Then I checked my memory status. I´m currently using up, 1 204 612 kb worth of memorychip. Is this happening to you ppl too? I don´t want to restart. Why should I ;) Is this some kind of an issue with client to eat up your memory stack?

Btw comp: Intel duo, Nvidia 7950 512, 2Qb ram etc 4 months old so hardware is suffient...

//MIKA

ps. last while I was writting 1 209 904.... total amount used memory for comp is now 2,07 Qb :)
Alicia Sautereau
if (!social) hide;
Join date: 20 Feb 2007
Posts: 3,125
04-11-2007 04:26
think it`s normal, my daily ram usage is usually around the 1gig aswell, dunno how much it would use if it didn`t crash once in awhile per day lol

2.5gig ram so not worried but it`s normal :)
Ketra Saarinen
Whitelock 'Yena-gal
Join date: 1 Feb 2006
Posts: 676
04-11-2007 08:41
SL has to cache and work with a *HUGE* amount of texture data. Because everything is user created, textures cannot be optimized, and have to be streamed to your computer. So SL is going to use up as much RAM as possible.
_____________________
From: Doctor Who
J: You've been to the Factories?
DW: Once
J: Well they're gone now, destroyed. Main reactor went critical, vaporized the lot.
DW: Like I said: Once. There's a banana grove there now. I like bananas. Bananas are good.


From: Clutch, 10001110101
Robot Lords of Tokyo, smile, Taste Kittens!
Darien Caldwell
Registered User
Join date: 12 Oct 2006
Posts: 3,127
04-11-2007 09:33
I have 2 gig of memory in my computer, and i've been considering adding more because SL will end up filling the full 2 gigs after extended usage (and finally crash). I'm convinced there's a memory leak, but LL obviously doesn't think so, or they would have fixed it by now (been there for ages).
Luve Schack
.:ShoeAholic:.
Join date: 30 Oct 2006
Posts: 84
04-12-2007 15:21
From: Darien Caldwell
LL obviously doesn't think so, or they would have fixed it by now (been there for ages).


That is the best laugh I've had all day. /holds sides tears streaming down her face.
Ee Maculate
Owner of Fourmile Castle
Join date: 11 Jan 2007
Posts: 919
04-13-2007 01:33
From: Luve Schack
That is the best laugh I've had all day. /holds sides tears streaming down her face.


Ditto :)
Meade Paravane
Hedgehog
Join date: 21 Nov 2006
Posts: 4,845
04-13-2007 08:06
From: Darien Caldwell
I'm convinced there's a memory leak, but LL obviously doesn't think so, or they would have fixed it by now (been there for ages).

Er.. Memory leaks are one of the hardest types of bugs to track down and fix. If there are leaks, it's because LL hasn't been able to find them or fix them without breaking other things.
_____________________
Tired of shouting clubs and lucky chairs? Vote for llParcelSay!!!
- Go here: http://jira.secondlife.com/browse/SVC-1224
- If you see "if you were logged in.." on the left, click it and log in
- Click the "Vote for it" link on the left
Nicholaz Beresford
The Mad Patcher
Join date: 14 May 2007
Posts: 70
05-14-2007 09:50
This may not be related to a memory leak (not saying that there are none). But see the comments on https://jira.secondlife.com/browse/VWR-364 from today and yesterday and try reducing the graphics memory in preferences, adv. graphics (use 256 or 128).
Amadyne Beresford
Registered User
Join date: 26 Feb 2007
Posts: 0
05-21-2007 08:34
Btw, a main source of memory leaking has been found and I'm running my own SL build beautifully then. There's another issue with large memory footprint, that is, unless you have 1.5GB or more of memory, make sure you set preferences, adv. graphics, graphics memory to 128 or 256. This effectively limits the size of the texture buffer (it'll still be 160 or 320MB (yes MB(!))) leaving more room for the leak until it's fixed.
Nicholaz Beresford
The Mad Patcher
Join date: 14 May 2007
Posts: 70
05-21-2007 08:36
Btw, a main source of memory leaking has been found and I'm running my own SL build beautifully then. There's another issue with large memory footprint, that is, unless you have 1.5GB or more of memory, make sure you set preferences, adv. graphics, graphics memory to 128 or 256. This effectively limits the size of the texture buffer (it'll still be 160 or 320MB (yes MB(!))) leaving more room for the leak until it's fixed.
Dnali Anabuki
Still Crazy
Join date: 17 Oct 2006
Posts: 1,633
05-21-2007 09:26
From: Nicholaz Beresford
Btw, a main source of memory leaking has been found and I'm running my own SL build beautifully then. There's another issue with large memory footprint, that is, unless you have 1.5GB or more of memory, make sure you set preferences, adv. graphics, graphics memory to 128 or 256. This effectively limits the size of the texture buffer (it'll still be 160 or 320MB (yes MB(!))) leaving more room for the leak until it's fixed.



Nicholaz, do you recommend installing the patch you posted in Jira for this? My system is bleeding edge (4G Ram, 2G Video nVideo 7950x2) so I am not having problems but my husband has been having some.
Nicholaz Beresford
The Mad Patcher
Join date: 14 May 2007
Posts: 70
05-21-2007 11:08
From: Dnali Anabuki
Nicholaz, do you recommend installing the patch you posted in Jira for this? My system is bleeding edge (4G Ram, 2G Video nVideo 7950x2) so I am not having problems but my husband has been having some.


If you have access to the source I'd highly recommend to build the CURL library again from the latest version on their website. Even if you have enough memory, the leak will be a drag on the whole memory management inside ... it made quite a difference here.

And with a less than fat system, setting prefs, adv. graphics to 256 or even 128 will be a big help too.
Learjeff Innis
musician & coder
Join date: 27 Nov 2006
Posts: 817
05-21-2007 14:36
Isn't the default 64? I run with 64 a lot, even though I have 2G, just because the world rezzes so much faster after a teleport to a new sim.

Even then the memory seems to keep growing, just not quite as fast.

I set it higher whenever there's a good reason, like a nice view, Spaceport Alpha, Japanese Gardens, etc.
Jacques Groshomme
Registered User
Join date: 16 Mar 2005
Posts: 355
05-21-2007 16:00
Didn't they establish a bit ago that there is a memory leak in the Mozilla implementation, and that there isn't anything that can really be done about it until Mozilla releases an update?
Nicholaz Beresford
The Mad Patcher
Join date: 14 May 2007
Posts: 70
05-22-2007 00:25
From: Jacques Groshomme
Didn't they establish a bit ago that there is a memory leak in the Mozilla implementation, and that there isn't anything that can really be done about it until Mozilla releases an update?


Dunno, I'm not on the source (or SL) for that long. But currently I can look at the leaking memory at the end of a run and the #1 ultra prime source for leaking was LIBCURL which has been fixed (as of March this year). The rest (I did not see any of that coming frorm mozilla) is either a one time thing (i.e. nothing that adds up) or neglectible.
Nicholaz Beresford
The Mad Patcher
Join date: 14 May 2007
Posts: 70
05-22-2007 00:27
From: Learjeff Innis
Isn't the default 64? I run with 64 a lot, even though I have 2G, just because the world rezzes so much faster after a teleport to a new sim.

Even then the memory seems to keep growing, just not quite as fast.

I set it higher whenever there's a good reason, like a nice view, Spaceport Alpha, Japanese Gardens, etc.


It's a trade off. 64 uses less memory and may rezz faster, but may cause more disk and network traffic (because they are building a cache in memory for the textures). So if you run around in a shop or stay in an area a bigger setting will make it unnecessary to read textures from disk and gets it from memory, which will be faster.