Frequet Out of Memory Crashes...???

Ive heard from a few people that this is happening alot. And its starting to happen to me! What is there that I can do to help this... I have more than enough memory on my system to handle SL. I had heard from a friend that there had been talk or a virus that eats away your memory, from SL. Anyone hear anything about that and/or could someone direct to a forum posting or blong that mentions this? Its just starting for me.. has happend move than 5 times this week alone and its worrying me as well as ticking me off!

Help!?!?!?

Thanks in advance...
Kimberly

i have 3 gig ram and i have it several times a day horrible.

recent sl versions have lots of memory leaks.
just set view range lower and it will leak much slower.

For the past month my system has been enlarging the size of it's page filing thingy virtual memory several times a day (when only SL [insert trademark/registered oogamywhatsit here] has been running). Now for the past 2 days I'm getting full on Out of memory errors.

So why suddenly does SL [Insert...yada yada...] take 2gb of RAM to run???

I thought I had a trojan...put on my deep sea diving gear and dove into my registry only to find all was well...no trojan, no spyware, no virii lurking... no reason bar SL [You know the drill by now]

This is a recent bork that I'm only just starting to experience....

I have 4 gigs - it's just this SL game. I can run high end games, photoshop, maya & max simultaneously , 2 painting programs a game editor, winamp, 3 messengers and 32 firefox pages all at the same time and never have mem problems, but with the SL game, I can't seem to run that just alone on any PCs I have here laying around here without it getting that error lately. I thought I saw it up in Jira or whatever too.

SL crashes when it reaches 32bit limit of what a program can handle, and does it use more ram more you tp around? yep.

Not plagued by ram crashing myself but i do get one usually in a week.

What can happen is this: Much of the OS unloads itself to make more room for programmes, however there are protected sections of memory reserved for parts of the OS that install a handle that then loads other parts of the OS when required/need to carryout API calls/functions. However, some not so well behaved programmes (can't mention their actual name, but their initials are SL ), wont give back control of that memory and then you get the message 'out of memory'.

This can be aggravated if you use a GC (Card and or Chip) that uses shared system ram.

Try setting the OS for background services and not programmes, in the performance tab. You can also try a memory optimiser, although they can cause issues themselves.

people need to stop saying its the os's fault on how it handles ram.
SL is the only program in recent history that has such a major memory leaking going on that i have seen.

" SL is the only program in recent history that has such a major memory leaking going on that i have seen."

Oh theres alot more then just SL , but its hardly the worst of the bunch.

You should try Hellgate, my 64bit client of that game used 3.98gig ram .

Ok so it didnt crash it just ate up ram cause it COULD (sl cannot go over 2gig ram without crashing) , and i glad it did, cause i never load much in it ever : p my friend thats on 32bit loads 4 times more then me ok so he only got 2gig ram ~.~

Seen this behavoir in way to many programs and games usually its blamed on those who make it but os is to blame to if it cant handle all the memory needed for caching/storing what its trying to render or do it will most of the time go into a adress space that is unreachable.

Tthe size of the virtual address space is fixed at 2 gigabytes (GB) for 32-bit applications, and SL reaches that very fast, a modern graphics processing unit (GPU) can have 512 MB or more of video memory.

Applications that try to take advantage of such large amounts of video memory can use a large proportion of their virtual address space for an in-memory copy of their video resources. On 32-bit systems, such applications may consume all the available virtual address space.

32bit bleh limitations -.- the 2gig limit nowadays is easy reached on most programs nowadays and same goes for games (wich SL isnt -.o)

Every time i hear the word "memory leak" it make me go >_> , yes maybe but the program will try to load everything it can into memory (good i hate loading screens) so you wont have to actually load it again, its just when it wont let go of it then you have a problem, and its rarly ever "fixed" and i expect it never to be.

-__- no i dont crash often of memory running out (the door?) , maybe if i tp around and stay in SL 8~12 hours it'll happen, but im usually fallen asleep by then.

Ultimately, it IS the OS that controls ram... no other programme that behaves within the recommended API calls, has the authority to allocate ram. In the bad old days, they had to introduce High Memory, whereby parts of the OS would be shoved into higher banks of memory so that programmes had more room to breathe. OS's these days use swap files (caches) to do much the same, however they still reserve portions of memory so that they can swap in and out various sub-programmes to control OS functions as and when required. This is more relevant with OS's since the introduction of XP, as being portrayed an OS that would not suffer the BSOD (Blue Screen Of Death), only badly behaved programmes would be frozen and you could save your work and restart safetly.

'Memory Leaking' is mainly due to badly behaved programmes, not releasing memory when told to by the OS, as the OS cannot then function, it freezes and gives the report 'Out of memory'. So often, programmes will keep hooks in memory on the basis that you 'may need to use them again'. DLL's being one type of application that can remain even after a programme has been shutdown.
Take a look at the many processes and services that are running on your system, even when you are not using them... msmsgr (MicroSoft Messenger) being one... QuickTime, Realplayer, Media Player, Remote Assistance etc etc. I always set services to manual never automatic, same with updates. I don't want them 'at the ready, just in case'.. setting them to manual means they are only turned on when I want to use them.

i know all about what a memory leak is.
it's simply somethig being created in memory and not being erased.
AllocMem and FreeMemory, new and delete, etc...
Wether its SL or opengl library i don't know but its not the OS's problem.

I started having this problem all the time in places with lots of avatars in multiple sims close together, specifically when I switched from Windlight to the Release Candidate.

Whilst I don't suffer memory leaks unless I'm using my OpenGL capture programme for machinima, I do get 'runtime library failures' after about an hour of capturing.. the basic probelem seems to be with .NET Framework. I have loaded the version 3.5 (beta) on some of my systems (I have 4) and they don't fail.
OpenGL platforms use .NET Framework, the vast majority of people are still using .NET Framework version 1.