randym77, The reason I ask is that I am a beta tester and have the release notes for the various betas... lots of them... notes which mention things fixed and known isses at each stage... including the notes for the release of the final version... and see nothing in there which validates your repeated claims of foreknowledge that there was a remaining memory problem or a major memory problem or any sort of remaining memory issue. If CL knew about it before release, it would be logical for them to want US to know about it so that isolation of the problem could help solve it. Say that I was QA'ing a game and heard that if a player walked backwards down the hall the monsters would turn psychodelic. I'd tell everybody working on the game to be sure to walk backwards down any hallways until someone discovered that it only happened on a certain floor or when holding a certain object. Under Known Issues would be "walking backwards/palette problem" until the trigger for it was isolated and stomped on. So you have no proof that this severe memory leak was even one of the things found when the disks were gold and in manufacturing? It could well have been found after it had shipped and got into the hands of thousands of users... at which point it is like words spoken and hanging on the air, a bit too late to retrieve. The guys at CL are still working at fixing things and still sending out updates, so it isn't like they are all sunning in Baja with funny parasols in their drinks. But, as mentioned above, the more concrete information they get back, the more quickly bugs can get squashed. It is possible that this isn't a single issue memory leak, it might be 2 or 3 memory bugs all exhiting the same symptom of crashing (is that red rash measles or chickenpox?... the patient who is itching doesn't care, but the doctor still needs the rest of the history before writing a prescription). Carolly