|
|
|
In truth, this problem existed way before 1.20. I'm currently using 1.19, and experienced this problem long before even this version. The client-side memory leak has been a known problem for at least 6 months (which is when I became aware of it) and from what folks tell me, existed long before that. It's been around long enough that many consider it poor system management it hasn't been located and corrected.
There is no indication in VWR-2997 that this problem has been resolved or fixed. The latest post to that thread indicates the problem still exists, and that post is marked SHOWSTOPPER. Thus, I am also changing the level of this post to showstopper. A severe memory leak that causes the client to continually crash and severe lag is about as close to affecting everyone on the grid as a problem can come.
Ah I understand now. I misunderstood the original posting.
You know what I think is the problem Harleen? Linden Lab's inaccurate choice of the word "resolved" for such issues. The matter is not "resolved" if the issue still exists. They may consider this post resolved, but surely they could think of a better word. Even "Closed" would be preferrable. Resolved makes people think the matter has been corrected... and this one certainly has not. Yes, it has been proposed that that be changed (WEB-247), to be fair though it is the makers of JIRA that choose this definition of resolved.
We have been investigating memory leaks for some time now. We have fixed a few, including a severe one that will be fixed in 1.21. It is unlikely that this will be "resolved" any time soon entirely. What would be more helpful than pointing out that there are leaks (we know that), would be specific reproducible circumstances that reveal rapid measurable memory leaks. We will be including some debug options to assist with this in 1.21.
Greetings Steve. As a systems analyst from way back, here would be my suggestions:
The memory leak is fairly rapid (not sudden, but progressive over a limited time), so the actual phenomena should be easily observable. The only way to trace this leak will be to set up an access computer by the testing and measuring equipment, and start playing Second Life. Have one person watch (and record) the stats while the other person uses numerous aspects of Second Life. Here are some things I would try: In all of this take before, during and after memory measurements, along with documentation as to what was just done. This methodology is the first step toward discovering WHERE the leak is occuring. Once you have discovered the primary direction, you can start ferreting out the source... and the solution. Most likely it's a piece of foundation software that isn't behaving properly. This method will take between 2 to 8 hours do to properly, and may have to be reapeated, so don't expect quick results. But as many problems as this leak causes, the time spent in hunting it down will be well spent. Still get these horrendous leaks even after a 3 month haitus. On a macbook pro, was using first look which never had this problem for some reason, however release client's always have caused a severe leak to the point of a hard reset.
Running an Intel Core 2 Quad, After Updating all of my drivers. i came into watching the amount of RAM SL was Taking up.
Within 5 to 10 minits. the program Hits over a Gig in Use. (Standing Still) same here. within a few minutes the ram is so high it locks the screen - and yes it can happen standing still looking at a white wall. running 2- 3.4gig pentium 4, and yes from above i am contantly watching my task manager to watch the memory go up. i can drop screen and reduce program memory usage, but Ram/VM will not reduce.
I agree. There is major memory leak at least in 1.20 series. I am using latest release version (1.20.16) and it seems to be leaking memory at a speed of 1MB per 2 seconds or so.
Had a major memory leak just standing in one spot , not building nor doing anything using version 1.20.17(98669).
Ram was low and steadily began to rise again not moving or tp'ing. Loaded task manager and watched memory rise this really needs to be fixed. I've discovered that when SL is minimized the leak slowly fills up my memory until it crashes, which takes about an hour or so. So far, with it maximized, the memory is fluctuating with a slower increase. I'll keep an eye out on my processes and report what I find. Ver 1.20 seems to be worse for the leak than the 1.19 viewer.
Here's what I'm running: Second Life 1.21.6 (99587) Oct 14 2008 17:42:25 (Second Life Release) You are at 280841.4, 262472.2, 33.1 in Quantum Acres located at sim5789.agni.lindenlab.com (8.2.35.91:13002) CPU: Intel Core 2 Series Processor (2400 MHz) Calia, the memory issue w/SL minimized was reported in
Thx! |
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
 |
|
Bug
Resolved
Showstopper
Severe SL memory leak
This a Release Client issue since the latest patch. Second Life 1.20.9 (88980) Jun 3 2008 19:25:06 (Second Life Release Candidate)