|
|
|
[
Permlink
| « Hide
]
alan edelman added a comment - 30/Mar/08 08:24 PM
Oh, and it doesn't happen of course on the Mac.....
Can you provide more details on your problem, e.g., the exact error message you see, or what happens on SL viewer after you clicked OK on the Windows' error dialog?
And, just for a curiosity, what happens if you remove some memory modules from your system and reduce the amount of main memory (hardware) to 2GB? (In case you can do it easily.) Since I have switched to the Second Life 1.19.1 (4) Apr 2 2008 11:59:37 (Second Life Release), I have also gotten an Out of Memory error as well. It has never happened before this release for me. I get three options Abort, Retry or Ignore..I have tried the Retry and keep only getting the message. If I click Ignore..SL may work a few minutes more...or crash imediately.
Enviornment: I also get the out of memory error every time i rum SL viewer, both on the RC Candidate and the current version. i do have the latest versions of both. this has been happening since the last version, 1.18. it does not help to reduce memory for other programs running, just prolongs the time between crashes. SL will use up all available memory (up to 2 gigs in Vista or XP) then give the message and crash.
This does not seem to effect my laptop, as it is not as updated as my desktop. This is my configuration>: running the RC Candidate, which has crashed already due to this. This is a fairly high end machine, and should have NO problems running this program at all. Second Life 1.19.1 (4) Apr 2 2008 11:59:37 (Second Life Release) You are at 261773.2, 301903.6, 26.2 in Isle of Kidd located at sim2852.agni.lindenlab.com (216.82.19.95:13005) CPU: Intel Core 2 Series Processor (2666 MHz) Same problem here.. as soon as SL approaches a RAM memory usage of 1.35 GB, the "out of memory" window appears. Depending on the surrounding in SL, this could happen after 15 minutes oder several hours, but sooner or later it happens. You can then choose "ignore" on the error-window for several times, which might sometimes work and give the chance to close SL regularly. If "ignore" does not work, SL crashes. Other than the original poster i dont have to reboot the system, just close SL and start again.
At the time the error happens, there is ALWAYS enough free RAM in the system - top usage noticed was 2.3 GB overall, with 4 GB installed (i know Vista 32bit cannot address the complete 4 GB, but at least 3.3 I think?) My system: While there may be some similarity to
I will note here (as elsewhere) that on my (HP) rig the crashes now tend to occur around the 3 GB wall that 32-bit apps are unable to transcend. (I'm running under the 64-bit edition of Vista Home Premium (and SP 1). Sysinfo from a newly opened session: Second Life 1.20.8 (88152) May 22 2008 15:26:00 (Second Life Release Candidate) You are at 286240.8, 265509.9, 102.7 in Huineng located at sim3510.agni.lindenlab.com (216.82.21.245:13001) CPU: Intel Core 2 Series Processor (2399 MHz) It does happen on the Mac ...however only when in bootcamp running XP, happens after an hour, and has happened only since this last update.
I have 4 Gigs of Ram on the Mac and loads of memory assigned to Bootcamp as I use it after hours for Second Life. @ Paisley Beebe
I'd count that as an XP crash then, still, not a Mac crash. Emulation software is going to also emulate all the wacky memory issues that XP most probably has built into itself (at least these are issues that also affect many apps other than SL, though not generally in exactly this way). I'm constantly noticing apps that can't seem to release their hold on XP (and Vista) memory once they've been run once. As an example, yesterday I found my Sony Vegas sessions (editing a fairly small video) hanging constantly after a few minutes' work. Whether this bad garbage collection is a fault of the programmers of the guilty processes or a fault of Microsoft for managing memory badly is hard for me to say as a user who happens to know a little about programming, but not enough to fix these issues. I do know, however, that not all programs leave telltale processes active in RAM when they are stopped. When I looked at the Task Manager I saw that there was a lot of extra junk in memory, mostly programs that had run hours ago and had left a footprint in RAM that I could only have eliminated by halting their processes. After a cold reboot of the system I had a much smaller core of system processes running, and Vegas ran more or less perfectly. I am getting the same memory error described by Tobyus Flannegan above. I'm running SL 1.19.1(4) under WIn XP Pro SP3 on an Intel T7400 @ 2.16GHz with 2GB of Ram and an ATI Mobility Radeon X1900 w/256MB. First encountered it walking the RFL yesterday.
I am getting the same memory error described by Tobyus Flannegan above. This has been happening every 20 minutes on the RC or production clients, for the past 2 months. I have tried strripping off all other processes in XP, reducing graphics in SL, removing all HUDS and attachments and clothing, making graphics preferences LOW, reducing my ATI card's graphics resolution, and generally tinkering with just about everything possible to reduce memory. It doesn't matter, it appears there is a memory leak and my SL process requires progressively more and more memory until it hits 1.3g and crashes (about 20 minutes into my SL session). I use three different machines to access SL, all laptops, 1 Dell and 2 Thinkpads. They react the same. All running XP. The one I am on now is verifiably XP 2002 SP3, on an Intel 2CPU core, 2.00 gHz, 2GB RAM. It doesn't matter if I am docked or not. Virtual memory is 1524MB.
is this still an issue with the 1.20.15 build or 1.21?
also since i dont think that strictly duplicates the other im moving the link to relates to instead I am having the same issue on the latest viewer.
Second Life 1.20.15 (92456) Jul 18 2008 10:58:42 (Second Life Release) You are at 215633.4, 257972.6, 28.5 in Esseex located at sim7758.agni.lindenlab.com (8.10.147.251:13001) CPU: Intel Core 2 Series Processor (2194 MHz) I am running the x64 version of Vista Ultimate with 4GB's RAM. It wil go to out of memory warnings at about 3.2 GB. Thanks to many of you who have attached your Environments. Can some of you also attach your Crash Logs and Name them with your name, so we can match them to your environments and see if we find a pattern? Can any of you also tell us if you have other programs running and if so, what?
I am adding the SecondLife.log, SecondLifeException.log, and the stats.log from most recent crash to this. hope it helps.
My logs from the latest crash.
Thanks Trenton! Can a few more people add theirs (with their names on the files and their environments posted it comments) so we have a variety to compare?
OK,
@alexa: is the crash reporter not sending you what you need to know on this? Because I've been diligent about letting the restarted viewer send them if, if it's pointless I won't waste my time. If you're looking for a pattern, you can start with fact that all this stuff is happening on multicore boxes, and a lot of them are Core 2,which is quad core. That suggests that the viewer memory management is not multicore safe. I pointed out in Soft Linden closed If the viewer memory management is not multicore safe, it needs to get that way Real Soon Now....because the viewer itself is soon reaching the level at which it will need multicore to be runnable at all. I can consistently repro this on my HP DV9700 Laptop, all I have to do is simply jack up my draw distance to 512 and wander around Second Life loading textures until I get the error. It's improved a bit in recent viewers so it takes longer now, but it still is reproducible. I can watch the memory go away in Process Explorer until it reaches 1.6gb of memory in use, then I'll get the smartheap error message. With the console up, each ignore has a corresponding error loading texture until the viewer crashes. In one instance, it didn't crash as I kept clicking ignore until the screen effectively went totally black as the textures failed to reload.
As a side note, memory usage in the SLVoice executable appears to be going up with every "connecting to voice" that happens, I've seen it go up significantly when I do quite a bit of cross sim flying on the mainland. Just had it fail again, so I figured I'd update the JIRA while I wait for my avi to time out.
Look at your crash reports, LL. this is not a freak occurrance. Second Life 1.20.15 (92456) Jul 18 2008 10:58:42 (Second Life Release)
You are at 173098.3, 285628.3, 380.7 in Harrington located at sim4707.agni.lindenlab.com (63.210.159.103:13000) CPU: Intel Core 2 Series Processor (2399 MHz) CPU: AMD (Unknown model) (2211 MHz)
Memory: 3072 MB OS Version: Microsoft Windows XP Service Pack 3 (Build 2600) Graphics Card Vendor: NVIDIA Corporation Graphics Card: GeForce 6800 GT/PCI/SSE2/3DNOW! OpenGL Version: 2.1.2 LLMozLib Version: [LLMediaImplLLMozLib] - 2.01.17689 (Mozilla GRE version 1.8.1.13_0000000000) Packets Lost: 613/447536 (0.1%) this has been happening to me since 1.20. on 2 GB ram, daily. i added another GB, now it happens only if i tp around a lot. If you run Vista, even three gig isn't enough to prevent it....especially if you're quad-core.
Interesting: Sougent Harrop commented on Already voted on the other issue. Don't know how easy the blasted repro has to be, I can reproduce it at will, it just takes time for the texture cache to fill up. Turn up draw distance to maximum, go someplace with lots of different textures, especially at the 4 corners of a sim so you can make use of all 4 of them, cam around (space navigator is good for this) for as long as it takes to get the memory usage up to 1.6 gb, wait for the error box. Do it with a console up and you'll see every time you click ignore you get a texture failed to load error. Not being able to repro shouldn't be an excuse for this one. ------------------------------------------- I find this interesting because I have a SpaceNavigator as well, and often the crash message comes up as I'm swinging cam (although I usually use alt + left/right arrow for that) The viewer is famous for not tolerating rapid cam movements well...and I wonder if it's because swinging cam while anything else is going on (and on 15Mbps fiber at 1680x1050 with four cores a lot can happen at once) tends to push viewer threads onto multiple cores simultaneously? Thus tickling a multithreading bug? We've continue to address memory issues in the latest Release Candidate viewer.
Please try the latest 1.21 Release Candidate and report back. You can download it here under Test Viewers: http://secondlife.com/support/downloads.php  Issue still occuring in 1.21.
Further, going into help and "About SecondLife" once actually on the grid causes a crash. 4 Crash reports sent. Second Life 1.21.0 (95157) Aug 26 2008 16:03:19 (Second Life Release Candidate) CPU: Intel Pentium III/Pentium III Xeon (0.25 micron process) with external L2 cache (2666 MHz) i have had this problem a long time and found out how ti fix it. go to edit, preferences, graphics then click the hardware options tab. in there bump the memory slider down to what your video card has or less. my was set for 2gigs and i only have 768. oh btw. the open GL that SL uses will not use more then 512mb it looks like. hope that sorts things out for you all. my computer has never had this problem since i changed that slider.
Hi Alan, are you still experiencing this after updating your drivers and trying the latest Release Candidate?
Alexa, I'm not trying to be argumentative but I'm very disappointed in the response to this issue. This has been a continual problem since viewer 1.19 was released. In many Jira entries, people including myself have commented that it seems to be related to the amount of textures and avatars being loaded in a given area. In an empty sim you can stay connected all day long. In a sim with 80 people you'll be pushing 1 gig of mem usage within 10 minutes. This issue is EXTREMELY easy to reproduce and occurs on both of my machines running different hardware configurations with the latest drivers. It hasn't given any indication of being a driver issue, instead it seems to be the way in which the SL client loads textures.
It needs to be noted that the 'texture memory' slider under preferences/hardware has a direct effect on max RAM usage indeed. Additionally, the client cache seems to have a direct impact on maximum viewer memory..the smaller the cache, the smaller the memory will stay.
with a setup of a 500mb cache and 64mb I have fought this issue since 1.19. Everything is great, fine and wonderful, then all the sudden start getting out of memory errors. I have inquired about it several times when speaking to Conceirge Support on other matters and always get the standard LL answer.."They are looking into the problem..." So with time, Ive just given up even reporting it other than crash reports. The problem occurs with current Viewer as well as current RCO and has since release of 1.19. I have tried updating drivers and even bought more RAM. All efforts to resolve the problem on my end have been unsuccessful.
Alienware Computer Thank you all for your feedback. Is anyone still experiencing this with 1.21? If so, can you please add your location, and repro steps to what you were doing, what other programs were running, etc.
Thank you! I have same problem after installed the new driver came with Geforece 9400GT (evga)
I tried many things and did not solve the problem. I went to the EVGA home page ( http://www.evga.com/support/drivers/ )and found the new driver on 9/25/2008. (Version 6.14.11.7813 dated 9/17/2008 )I installed it and defrag the HD, my system works 200% faster and working perfect now. Thank you. /////////////////////////// My system info: CPU: Intel Core 2 Series Processor (2326 MHz) By the way, on 1.21 you don't get an explicit out-of-memory error, it just crashdumps. I opened VWR-8841 because the symptom changed, but nobody's watching that one.
Just reproduced VWR-8841 again with 1.21.3 Repro: Go to Ahern Welcome Area (always has many avs at a sim corner) . Cam around rapidly (orbiting rapidly and zooming in and out with a SpaceNav is good).Watch as memory climbs above 2gig. Then crashdump happens. Experiencing same... using new HP HDX9494NR.
Last occurred in Hedge 115, 15, 31 Second Life Server 1.24.7.98039 Seems to occur anywhere after I've been in world for more than an hour or two (varies). Runtime Error Microsoft Visual C++ Runtime Library Second Life 1.20.16 (97603) Sep 24 2008 18:30:45 (Second Life Release) CPU: Intel Pentium III/Pentium III Xeon (0.25 micron process) with external L2 cache (2094 MHz) Experiencing the "out of memory" error:
CPU: Intel Dual Core P7350@2.00 GHz The later issue VWR-8841 is marked Fix Pending re RC Viewer 1.22
Please would reporters of this issue try the latest RC Viewer which can be downloaded from here Release Candidate Test Viewers If you still have an issue, please reopen [left sidebar] and add your full computer environment, Help > About Second Life, including the Viewer you are using and the Region(s) where you have this issue. Please also include the Graphics Card driver version you have. For technical, time-sensitive and/or Region/Account specific issues please Submit a Ticket with Support Thank you : ) |
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
 |
|
Bug
Resolved
Critical
Out of Memory Error 
texture memory (which works fine by the way), my client reaches about 1.2 gig of ram usage after hours and hours of play, without getting into crashes due to my ram being full with a 1 gig cache and 512mb texture memory setting.