There is a known, severe memory issue with the Second Life Client. However, I don't believe it's a memory *leak, I believe it's memory bloat. I'm only posting this issue at the request of DigitalBlack Jackhawk, and in the hopes that this might help fix the issue, as I don't believe it's been fixed because it hasn't been accurately identified. Quickly Described: All primitives have dynamic face assignations. When the primitive changes, the faces change. When a face changes, it has to be reassigned, dynamically, in memory. The problem with this approach is that the memory allocated for the primitive actually has to change to match the new information. If this isn't handled correctly, IMO, you will get exactly what looks like a memory leak. Explanation: If you create a box in world, then check it's face assignments, then add a cut the faces change. Add hollow, and they change again. Each time this happens, memory has to be reallocated for this new information. If the SmartHeap Library cannot handle the dynamic reassignments, for whatever reason...crash. While I understand that it was initially designed this way, most likely, to save rendering(IE, a face that doesn't exist doesn't hit the asset server asking for textures and other information), I think it's a backwards approach. Assigning a null value to a static array for that face would accomplish the same task, while allocating memory for use when and if that face is rendered.