marbles of death!

When, oh when Linden Labs, are you going to release a version of Second Life for OS X that doesn't go into a coma every few minutes? To wit:

I have now had the viewer running for 300 seconds, and have hit 600,000 page faults and counting---quickly. Also, it appears to be attempting to actually write to swap (the page file on OS X), even though I have 4 gigs of RAM, and the application itself is taking up less than 400 megs in memory.

Enough with the direct ports, Linden Labs. Plainly, that approach doesn't work. You're going to have to actually put some effort into this.

Here's some motivation: The darlings over at Lucas Arts have now successfully *entirely* re-written both the physics and rendering engines for "The Force Unleashed" (to be released very soon)no fewer than FIVE times for no fewer than FIVE completely different architectures, including the PS-3, which is notoriously difficult to program for. And they did it in less than nine months.

Seriously. You're embarrassing yourselves. Make it work. We can't want this more than YOU do.

just sounds like your client or some reason is not using hardly any of your systems memory. Is enough of your 4gb free? 600,000 page faults sounds quite high for a 4gb machine in 300 seconds... should be much lower, if any. That doesn't sound like its totally a SL issue though, you might have other issues going on. Its not a surprise its using virtual memory though, thats what a page fault is all about...

It's a SL issue. When it happens, more than 2 gigs of memory are free. And I understand that I should have many fewer page faults when running Second Life, and in fact, in general. When it happens, it is the ONLY application that is paging out to a disk. Everything else is doing it properly, straight to allocated RAM.