• All submissions to this site are governed by Second Life Project Contribution Agreement. By submitting patches and other information using this site, you acknowledge that you have read, understood, and agreed to those terms.
Issue Details (XML | Word | Printable)

Key: VWR-1740
Type: Bug Bug
Status: Open Open
Priority: Critical Critical
Assignee: WorkingOnIt Linden
Reporter: Dael Ra
Votes: 22
Watchers: 10
Operations

If you were logged in you would be able to see more operations.
1. Second Life Viewer - VWR

Progressive increase in SL viewer memory footprint / decrease in performance when TPing between busy areas

Created: 14/Jul/07 02:09 PM   Updated: 25/Feb/09 12:31 PM
Component/s: Performance
Affects Version/s: 1.17.1, 1.17.3, 1.18.3.5
Fix Version/s: None

File Attachments: 1. Text File SecondLife.log (112 kB)
2. File SecondLife.old (1.26 MB)

Environment:
ASROCK Dual SATA2, AMD 64 x2 3800+, 4GB RAM. Radeon x1950XTX(512MB)
Windows Vista 64 Ulitmate / XP 64, Catalyst 7.6
Issue Links:
Relates

Last Triaged: 21/Jul/08 12:24 PM
Linden Lab Issue ID: DEV-19403


 Description  « Hide
Every time I TP between busy sims, the memory footprint of secondlife.exe goes up by around 250MB until it gets to around 1.6GB at which point SL crashes.

As the memory footprint increases, the viewer becomes more and more sluggish until it becomes unusable for navigation (response time in secs/frame)

This does not happen TPing between quiet sims.

Reproduceable routine (settle time is approx 10mins each time).

I log in to my skybox in the middle of knowhere and let the memory footprint settle . Settles at around 0.38GB.
TP to a busy area (eg Bad Girls), wander around a bit and wait for footprint to settle - 1GB
TP back to quiet area and wait to settle - 0.52GB
TP back to busy area and wait to settle - 1.2GB
TP back to quiet area and wait to settle - 0.73GB
TP back to busy area and wait to settle - 1.4GB
TP back to quiet area and wait to settle - 0..96GB
TP back to busy area and wait for footprint to reach 1.6GB - *crash**

It appears that some memory is not being reclaimed after visiting the busy areas.



 All   Comments   Change History      Sort Order: Ascending order - Click to sort in descending order
Nicholaz Beresford added a comment - 15/Jul/07 02:00 PM

I've seen higher than usual memory usage today. I'll do a leak check ...

Nicholaz Beresford added a comment - 15/Jul/07 02:16 PM

Confirmed.

Dale, sorry that I didn't take your report more serious (well I'm not a Linden but I'm the Leak guy). I should have just tried it when I saw it at VWR-1418.


Nicholaz Beresford added a comment - 18/Jul/07 08:20 AM

As far as I can tell, this is a combination of VWR-733 and VWR-1769

Nicholaz Beresford added a comment - 26/Jul/07 05:32 AM

Yes, there seems to be another leak or bubble inside the viewer besides VWR-1769. Question is only what makes it arise.

I have posted a description about normal vs. excess memory consumption:
http://nicholaz-beresford.blogspot.com/2007/07/about-viewers-memory-usage.html

What I need to find out now, is what specific activity makes the viewer grow beyond normal (because it does not [at least not to any excess] happen here).

If you want to compare notes/activity/hardware/whatever, please do so in the comments to VWR-851


Rascal Ratelle added a comment - 21/Oct/07 09:34 AM
Second Life 1.18.4 (0) Oct 18 2007 14:40:16 (Second Life Release Candidate)

You are at 283429.6, 267902.9, 55.2 in Pahto located at sim3358.agni.lindenlab.com (64.129.45.123:13004)
Second Life Server 1.18.3.71877

CPU: PowerPC 7450 (1249 MHz)
Memory: 768 MB
OS Version: Darwin 8.10.0 Darwin Kernel Version 8.10.0: Wed May 23 16:50:59 PDT 2007; root:xnu-792.21.3~1/RELEASE_PPC Power Macintosh
Graphics Card Vendor: NVIDIA Corporation
Graphics Card: NVIDIA NV34MAP OpenGL Engine
OpenGL Version: 1.5 NVIDIA-1.4.18
LLMozLib Version: 1.1.0 (Mozilla GRE:1.8.0.12_0000000000


Jennifer Christensen added a comment - 06/Mar/08 09:31 PM
I am not sure this is the right bug to post this in, but ever since I downloaded 1.19.0.5 I am seeing this issue:

Log in, and over time (30 to 60 minutes) - even if just sitting in 1 place and not moving, the SL Client gets slower and slower and bogs down. Checking Windows Task List shows SL to be using like 95Mb of RAM at 1st. But, over time, it keep climbing like crazy, usually I see the slowdowns when it gets over 300 Mb.

I am in Windows XP, with 2 Gigabytes of RAM, and using version 1.19.0.5 SL Client. Nvidia 8600GT video card. Athlon64 CPU 3 Ghz.

The only fix is to log out often and log back in.


Amurtigress Korobase added a comment - 08/Mar/08 05:37 PM
Hello,

I have tried troubleshooting SL on Windows Vista 64 mainly for six weeks now on my rather top notch PC.
I cannot exclude that everything might be fine on Vista x86, but the odds are, the issue will persist.

The symptoms are that in Vista Secondlife would not purge data accumulated previously when going through various Sims. The used amount of RAM might decrease a bit throughout the usual use but after roughly 3-4 hours SL takes up 1.5 GB of my system memory and crashes with a "Out of heap memory" error.

After the second or third time SL would crash my whole Vista after a random period of time, freezing the graphics output to a point where I am forced to push the reset button.

In Windows XP and 2003 SL will just purge all unneccessary data and leave a footprint of around 54 MB when minimizing the window, and start increasing from there again. No crashes whatsoever.

Suffice to say this puts my data integrity at risk under Vista. I'd be glad for any help on this.

Nicholaz: Feel free to get in touch with me in German or English, there is a whole bunch of things I tried to resolve the issue. To a point where this is driving me crazy now. I hope I can help resolving this

My system configuration:

Second Life 1.19.0 (5) Feb 28 2008 17:18:12 (Second Life Release)

You are at 248219.0, 286867.6, 256.7 in Wisconsin located at sim5571.agni.lindenlab.com (8.2.34.127:13006)
Havok4 Beta Server 1.19.1.81747

CPU: Intel Core 2 Series Processor (3942 MHz)
Memory: 4095 MB
OS Version: Microsoft Windows XP Service Pack 2 (Build 2600) (NOTE: I was running SL in a compatibility mode for a test)
Graphics Card Vendor: NVIDIA Corporation
Graphics Card: GeForce 8800 GTS/PCI/SSE2
OpenGL Version: 2.1.1
LLMozLib Version: 1.1.0 (Mozilla GRE:1.8.0.12_0000000000)
Packets Lost: 0/1246 (0.0%)
Viewer Digest: 6b1bac12-2a86-e1f2-aa5e-3108db5c8eeb


Dolfke Barbosa added a comment - 13/Jul/08 08:03 AM - edited
RC13 1.20 ... still no fix for MAc users ... ??????????

Modelnaam: MacBook Pro
Modelaanduiding: MacBookPro4,1
Processornaam: Intel Core 2 Duo
Processorsnelheid: 2.6 GHz
Aantal processors: 1
Totaal aantal cores: 2
L2-cache: 6 MB
Geheugen: 4 GB
Bussnelheid: 800 MHz
Opstart-ROM-versie: MBP41.00C1.B03
SMC-versie: 1.28f1
Serienummer: W88120UHYP4
Sudden Motion Sensor:
Status: Ingeschakeld

Chipsetmodel: GeForce 8600M GT
Type: Beeldscherm
Bus: PCIe
Breedte PCIe-baan: x16
VRAM (totaal): 512 MB
Fabrikant: NVIDIA (0x10de)
Apparaatcode: 0x0407
Revisiecode: 0x00a1
ROM-revisie: 3212
Beeldschermen:
Kleuren-LCD:
Beeldschermtype: LCD
Resolutie: 1920 x 1200
Diepte: 32-bits kleur
Ingebouwd: Ja
Core Image: Hardwareversnelling
Hoofdbeeldscherm: Ja
Synchrone weergave: Uit
Online: Ja
Quartz Extreme: Ondersteund
Beeldschermconnector:
Status: Geen beeldscherm aangesloten


Alexa Linden added a comment - 14/Jul/08 03:17 PM
Can someone provide a description of where they were teleporting and some numbers for memory at each step?

Chalice Yao added a comment - 15/Jul/08 12:02 AM
There's an important thing to remember when rapidly TPing between sims:

If you TP from one busy sim to another, the busy sim you've just come from still fully exists in client memory. A fun way to test this is to push your draw distance to 512, and TP from a mainland coast sim to an island sim that's one or two simspaces away. Looking at the horizon, you see the sim you just came from (you'd normally never see it from the island), slowly falling apart and vanishing.

This process can take up to a minute or more.

Thus, if you rapidly tp between 2, 3, 4 busy sims, it can be that at one point all of those sims objects you saw are still in memory, and the usage of course will rapidly rise before falling down again.

I'm not denying any memory leak. over time there just seems to be a certain memory threshold that can't be gotten below again, that is slowly rising..but don't confuse the memory usage when rapid-tping with that :>


Alexa Linden added a comment - 22/Jul/08 12:38 PM
Thank you all for your comments and information. because this originally a bug regarding an older version of SL, we always suggest making sure you are using the latest Release Candidate.

We are aware of the issue relating to memory leaks are currently working on this issue


Squirrel Wood added a comment - 11/Aug/08 12:16 PM
I have seen the client (up to 1.20.15) eat up more and more of the swap file over time. When you stand still for some time with most of SLs memory requirements located in the swapfile (despite 1GB+ of ram being FREE) the camera view starts to hang/stutter when you move it around while SL wildly swaps content in and out of the swapfile.

Alexa Linden added a comment - 11/Aug/08 03:41 PM
Hi Squirrel, How long does it take before this happens to you?

Rich Greenberg added a comment - 02/Nov/08 06:32 AM
We have this issue too (Dance Island)
On the dancefloor (very busy area with often 100 avatars). It's imposible to TP in or out.
Fly to another spot on the same sim solve the problem.
This issue showed up since the newest viewer (the one you must download to continue).
Since this this viewer, we suffer a dramaticle preformance drop.
(TD's <0,1) before the new viewer it was much better.
In this post I see other busy sims has this issue too. Wondering if there is anything to do in the sim itself?

Steve Mahfouz added a comment - 25/Feb/09 12:31 PM
I wish SL would fix this issue. My current SL viewer is the official one (Second Life 1.21.6 (99587) Oct 14 2008 17:42:25 (Second Life Release). I will start out with SL consuming about 250 mb of RAM and then escalating up to 900 mb or higher.