Memory Leak in Linux-Native Client?

Yes, I see this, too. After several hours in-world the system becomes more and more choppy, screen freezes occur more frequently until at one point the whole system basically comes to a halt and the harddisk starts swapping like mad. I usually quit the client when I see it starting to crash, so I don't have to wait 10 or more minutes until the system has recovered.

I find it happens more often when you zoom out with the camera a far distance to see more of your surroundings.

I have the same in Windowed mode. I have a system monitor on my KDE Kicker. As I go around, it goes up.

I'll look into it!

There does appear to be something causing memory usage to go up. The Heap for SL seems to endlessly grow with the heap growing past the allocated disk cache size. The number of files and locations open doesn't increase either. Only the heap. 0000000009ed8000 599392K rw--- [ anon ]
The more places visited the bigger this gets and it only appears to be accessible to a destructor when the client itself closes.

Thanks for the log, Llauren. There's nothing unusual there sadly (I've looked into the 'this should NEVER happen' message and I'm pretty sure it's actually harmless from a stability angle, but I'm checking with some other devs).

I've been working on the automated crash reporter lately which should help a lot in scooping up these 'random' crashes.

Thanks for looking at this. However, growing memory usage isn't unexpected behavior - to an extent this is expected over a session as SL's various in-memory caches fill up; 600MB for example sounds quite normal (assuming you have more than 512MB of memory!) and does not constitute a leak.

Indefinitely-growing memory usage would be unexpected though, as would heap usage far in excess of physical memory.

The longer I stay logged in the larger it gets. The client does slow down after a while though I have a massive amount of memory and I have never been able to fill it up before the client crashes. 2gb of ram then 6gb of swap, best I can do is get it to about 4gb of swap after eating all the ram, things get very unhappy and running pmap on it tends to crash it before it gets a reading. If there is something better than pmap then I can certainly use that. About the max it seems to grow for me before segfaulting is 1.2gb with 600mb being the average.

--

From behavior in world it appears that once an avatar has left the area the data for that area is still kept. Such as crossing over into a new sim or a teleport. The allocated memory continues to grow, it doesn't appear that any is released. If the disk cache is set in the client why not allocate the whole disk cache at client start so it may use continuous memory? Though it is quite possible as well to have a memory leak outside of the bounds of pmap, though the system should try to reclaim that. For some folks it does appear to happen faster. To get up to 600mb for me took about four hours.

Does everyone who is seeing this (and is sure that it is because of memory growth and not other random crashes) have 2GB of RAM?

I see this myself and I have 1 GB of RAM, 256 MB VRAM.

Specs in my sig. I'm seeing this.

Immediately after logging in, the client starts eating memory. It uses 757mb of ram and 2.2gb of swap in about 2 or 3 minutes. Everything slows down until the system is unusable, and the SecondLife client dies.

System Specs
=========
Ubuntu 6.10 (also tried with debian unstable)
Kde 3.5
kernel 2.6.17-10-generic
frglx graphics drivers
128mb video ram
Athalon 1.4ghz

I spent most of my time in SL far above the clouds, with only a few small objects in view - the little platform I stand on.
It runs at 40 to 60 and above FPS, really smooth.

However, once I spend a little while on the ground, specifically in fairly crowded areas, the FPS drops radidly and the whole thing starts to slow to a crawl, after an hour or two it's practically unusable and I hit teleport home to get back to 500m high, at which point the lag goes away.

Specs:
Kubuntu Feisty Testing
AMD64 3500+
2GB ram
ATI X800XT PE 256MB

My Slackware 11 install has shown serious disk thrashing after a few minutes logged on since about three client releases ago. The latest release bogs down to a grossly slow response in minutes. If I stay on any longer and my system may lock up.

Earlier releases (about three weeks ago) weren't nearly as bad. I was able to build a house and wander around freely with little problems, though my disk did show heavy accesses.

I can confirm this, as well, in the current 1.13 release series. After probably 10 minutes of use, my system RAM is completely gone and it begins swapping out. My system has 512MB of memory and I have nothing else running aside from Second Life as to keep memory usage to a minimum.

In the 1.12 release series this problem did not exist. In fact, it was fantastic. I rarely ever had to relog, but with the current 1.13 series I need to relog every half hour, or less, or my system will completely lock up.

I cannot provide any distribution information here as I built my system myself. However, all of my software is current, as well as stable.

Edit:
I should also mention that I am using an nVidia graphics card with the official drivers (1.0-9631).

Also, I have tried various combinations of LL_GL_BASICEXT, LL_GL_NOEXT and LL_GL_BLACKLIST; all to no avail. The memory leak is consistent in all cases.

I suspect it has something to do with textures, as the climb in memory usage is the greatest when I am in texture intensive areas. Also, forcing textures to rez by using the usual click method will greatly increase the amount of memory used. I can monitor this climb through various sources (gkrellm, top, etc.). At no point does the memory usage decrease.