Some people have NEVER hit the memory leak, and didn't know there was such a thing until after release and the high-end users with complicated scenes complained. After months of using it, I finally got it to crash, while beta-testing something else, and it was due to my error in saving/applying a pose where some of the information was in an external file. Neither of my testing systems (4-year-old PC and new MacMini) has over a gig of ram and both are spotless (Poser is the only application besides newly-installed operating systems) and neither is connected to the Internet. They are set up as working beasties, not game machines. Winnowing down exactly what causes a problem and being able to repeat it is the only way to fix it. Unless each of you tells CL your system specs and what you were doing when it crashed, it makes defining a bug that much more difficult. How do you determine the common denominator without data? Ranting over losing a file makes you feel better, but it does nothing towards solving anything. We all hurt when time is lost. So, what else did you have running (your toolbar(s), other applications)?, how many hours did you have it going? was it running hot? were there any warning signs? any error messages? how many figures or approximate polygon count? were you calculating hair/cloth or rendering a final scene? and, of course, your system specs. Maybe it only happens to scenes with dynamic hair on gen 3 figures with oodles of third-party morphs shot with no backdrop for the depth-of-field calculation, or maybe it only happens if Poser is fighting for memory with the browser because you were downloading a movie-trailer while rendering, or maybe it only happens if there are > 144 separate mesh units in the scene regardless of whether they are objects or figures, or maybe it only happens with a certain lighting rig and cast shadows with a particular video card and more than 2 gigs of ram. If you have a repeatable bug, the best solution is to use the contact form and let CL know what happened. Calmly and clearly. They will keep working on tweaking this, but you can either simmer on the boards or you can help by giving them the necessary data. Carolly