There are still very serious memory leak issues with all Second Life clients. For me, a user with 1 Gig of memory, having Mozilla open with many tabs (multiple web sessions inside a single window), and/or being on Second Life in a sim with a certain number of people nearby, and high number of objects and attachments present, will cause SL to crash for me.. either the client screen simple disappears and I get the crash-report sending request dialog, or the SL client window goes completely white, and I have to kill the second life client process and start it over again. These crashes happened constantly over Halloween (October 31, 2007) - they happen every day I use SL, but this date is notable because parties were happening all over SL in the evening and a number of us users were constantly crashing when we attended. I need a linden to look over my history of crash reports from the past month and a half and determine why this is happening. I also want to point out that these continued crashes have been plaguing other users, like Delmore Oh, and for a significant number of the Second Life population, Second Life is no longer usable or enjoyable, or we are forced to go to nearly empty sims with a reasonably low number of prims and scripts present to avoid crashing. These problems started with either the previous update, or the one just before it, and they seem to affect ALL SL clients, whether made independently using the Open Source code, or if they are the Linden's own Release Candidate Client. A good way to induce a crash seems to be to use the Inventory window sometimes, but it will happen on it's own anyway, without any actions. SL will also eat up memory so other programs crash, and the Windows Explorer Operating System says the Virtual Memory needs to be resized - I have never seen it have to say this before, and never seen behavior like this since the memory leak problems caused by newer AOL and AIM software I tried using on Windows 98 Second Edition (which would cause the OS to crash every 10 minutes and is what forced me to abandon Windows 98 years back and finally totally switch to XP). If I am an area where the crashes are not happening, and then a new person arrives, something about the person (an attachment?) causes me to promptly crash, and crash repeatedly while they are present, and I have to go someplace else. This obviously shouldn't happen, and I shouldn't have to ask them to leave or remove something. It's a bug. This has been the worst past 2-6 weeks for me in Second Life, with the game pretty much impossible to consistently enjoy anymore. Crashes are repeated, constant, and have made Second Life nearly unplayable. This issue needs IMMEDIATE attention, because of the constant crashes I cant buy anything, build anything, depend on anyone or anything in Second Life anymore. It simply is not working for me, and I would at least like a simple explanation why. I have not received any response from Customer Support, which may now be non-existent. I have no idea why my computer is crashing but it does seem to be directly memory-leak related, in Windows XP. I have ceased using Second Life and gone back to MUCKing, using instant messaging, and now playing games or watching videos, when I'd rather be on Second Life, but I just can't use the game anymore. It's become nearly impossible. I believe enough crash reports have been sent in by me (I don't always send them anymore) to merit some kind of explanation for what is going on, but for me and other users of second life this has been a nearly complete disaster. It is now unbearable. NOTE: This applies to Second Life regular client version 1.18.3.5, and Release Candidate version 1.18.4.1. UPDATE (11/8): Problem still exists in Release Candidate version 1.18.4.2. UPDATE (11/8): Problem still exists in regular Second Life client version 1.18.4.3. UPDATE (11/8): I have been told to "refresh everything" (Clear internet cache, SL cache, and cookies in the SL client Preferences and restart), "manually clear your cache" (delete all files in the SL cache folder in the hidden Application Data folder), and even to "use the Nicholaz Edition of the Second Life Viewer" ( http://nicholaz-beresford.blogspot.com/ ), and "set video memory to 16 MB". But the thing is, *I simply should not have to do these things* (even if they would work, which I doubt). This is very clearly a bug in SL. It NEVER happened before 2-6 weeks ago. Never. UPDATE (11/9): Neither clearing all caches nor running the Nicholaz edition (1.18.3.2/18xh) of the SL client seem to help avoid these crashes. UPDATE: (11.10) Users Anowyn Kembla and Yiffy Yaffle also have dealt with this problem. Also, someone told me it had to do with the Virtual Memory "pagefile" but I kind of doubt it. UPDATE: (5.22.08): While I have since completely changed my system hardware (Windows XP Pro SP2, 4 GB DDR2 RAM, 3.39 GHz P4 with GeForce 7800 GT 512 MB Video, GIGABYTE GA-N650SLI-DS4L LGA 775 NVIDIA nForce 650i SLI ATX Intel Motherboard) and I personally no longer have memory leak problems, friends of mine still report them, and it is clear that there is a kind of "Russian Roulette" that Second Life plays with systems, and certain system configurations cause memory leakage, and some do not. It would be very nice if a consistent pattern and cause could be determined by the Linden staff who look at hardware profiles and crash reports, to determine why these memory leaks are happening for a significant portion of Second Life users. This should be a top priority issue, because dedicated SL users are being seriously affected.