Constant freezing

It's not just Mac-related. For about two weeks I am experiencing a LOT of crashes each day on Vista and Nvidia Geforce 7600GT. On all viewers and with every Nvidia driver version that I tried. It's just crap!

I get this as well and I run an intel macbook with integrated graphics.

Forgot to mention... but if this issue is affecting you you should cast your vote!

http://jira.secondlife.com/browse/VWR-2358

Pretty consistent issue with my MacBook Pro 2.4GHz machine, lots of spinning beach balls. Thought it might be wi-fi so I grabbed a giant CAT5 cable and ran it into my bedroom, still get the same issue. The most stable of the clients has actually been the latest test viewer, with the bandwidth reduced to 1000kbps instead of 1.5. I wish they would spend more time on the client for Mac users.

With my Mac Pro 2.66GHz Quad machine, running 256MB of video ram as well, and 5GB of RAM, I have to use the last pre-Windlight official release in order to stay online and not spinning beachball into death. Even still it occassionally just goes "POOF" and unexpectedly quits when I am doing nothing at all, standing still. Very frustrating at times. That machine has a dedicated WinXP drive on it and using bootcamp I launch it and SL runs flawlessly. Same hardware, different OS. That tells me all I need to know about which viewer has the most attention paid to it.

Sure is frustrating. Just crashed again. I crash on the MacBook consistently. Running lowered video settings, using direct cable not wi-fi, lowered bandwidth settings in client. Its pathetic. And if the MacBook Pro gets hot, forget about running SL at all.

Im on a Mac Pro too, 2.66 Quad with 7gb ram.
Any Windlight client was really bad with my ATI X1900 so I upgraded to the Nvidia 8800GT and now I have the freezing and pausing :/

I thought the new card would help stop SL logging me out whenever I try to TP or cross to another sim...its just the same.

Running SL in XP via bootcamp really shows what the hardware can do, Sim crossings are almost unnoticeable and TP's seem to work all the time.

What is actually happening when we TP or cross a sim that is be so hard to do in mac os?
Could it be hanging trying to connect to a server? or is it the loading of the new sim under the blacked out tp screen?

Im using a really old 1.18.3 open source client as its the only one that is really stable for me right now.

Sad, isn't it? Really.... frustrating to boot.

I use smcFanControl to help with heat. Its freeware.

i have created a jira for a closly related if not the same issue type.

the problem is poor coding in the mac viewers.

Also LL puts an Intel and a PPC mac versions in the same down load or uses a generic mac format for both plat forms.

http://jira.secondlife.com/browse/VWR-5632


please open a new jira issue for this topic as that will get lindens to look at it. posting this here will not reach the lindens nor will LL work on or review any issues reported in the forums.

Have you guys seen this page on Wiki?

http://wiki.secondlife.com/wiki/Help:MacBook_Pro_2007_Graphics_Freeze_Workaround

I have a Macbook Pro with Leopard and I had a horrendous time with crashing and freezing the first two weeks on SL. I was on the verge of packing it in. Then I started running the clients via OpenGL following the instructions and as if by magic, everything stablised. Don't get me wrong, I still crash and freeze once in a while but probably no more than people running from other platforms or hardware.

Apologies if this had already been mentioned, but it works really well for me.

Yes getting the same with my Mac Mini.

im hoping the dropping of panther support will help speed up issues. http://blog.secondlife.com/2008/05/05/working-on-the-right-things-considering-os-x-panther-support/

please report this in the issue tracker

What would be better is splitting the Mac Client versions, one for PowerPC and one for Intel. Universal binaries are by necessity slower.

I freeze alot too with my year old macbook pro-but the worst problem i have is in logging out.
I can wait four or five min for sl to do it or i can force quit or if that fails force restart my laptop. SL is getting to be less fun all the time.

how is it possible for LL to keep releasing new viewers, yet this fundamental bug that seems to affect the majority of Mac users (any model) doesn't get any traction?

SL was totally unusable on this MBPro from June2007 when i bought it, until Feb2008 when the "Leopard Graphics Update" came out. Since then, I got a taste of what its actualy like to be a Mac SL user. and it sux.

i'm joking, but from where i stand, it doesn't look like anyone in LL actually bothers to test the Mac version upon each release. if they did (and had a decent work ethic), they'd never release this crap in the first place.

i think there should be a moritorium on ALL new features until the majority of these show-stoppers are fixed. is that unreasonable? not if you're a Mac user!

I've been looking at the debug console in RC8 and when i have the small 10 second pause i get a few lines like this after if unfreezes,

"INFO: checkPacketInID: packet _out_of_order - got packet 30081 expecting 28803 from 216.82.18.109:13000"


But after the long 60 second pauses i get a screen full of this,

"WARNING: LLURLRequest:rocess_impl: URLRequest Error: 6, 6,"


I'd post this on the jira but they seem to keep setting this to resolved on all the mac pausing issues i could find :/

It feels like they aren't even looking into this problem.

What is it going to take to fix this? I can't afford to take legal action but I'm guessing that is the only thing that might work.

HOW THE HELL IS THIS A DAMN SOLUTION???????

WINDLIGHT DOES NOT WORK WITH THIS CRAP!!!

How do you file a class-action lawsuit?

All I will say is people suffering from the constant freezing issue, check your CPU temp! If you are running hot this is EXACTLY what will happen. If I remember correctly these Macbooks which seem to have the majority of the problems were all reported to run hot. The Intel CPU's automatically adjust clock speed if they get too hot. This never caused an issue for me on anything BUT Second Life. I highly recommend a program called Temperature Monitor. I discovered for the last 6 months my CPU has been averaging 90 degrees C! It is a testament to OS X that the only place I did notice it was Second Life. As soon as I fixed the cooling issue my system dropped to about 54C under load. Second Life went from running like a stop motion film to an extremely smooth environment.

This is absoluely a known problem on the Linden Lab side, and they have absolutely no plan to fix it, because they're blaming Apple's NVIDIA driver. This will forever be a problem, and you will always have to deal with it.

Then it is a matter of filing a class-action lawsuit against Apple. Because if they are advertising that the MacBook Pro has an NVIDIA 8600M GT GPU in it, then people are going to make buying decisions based on the fact that it has that processor. Then if they do not have properly-working drivers for this GPU, for 8 months, then they "fix" it, and it still barely works, then they should reimburse everyone who WASTED THEIR MONEY on this computer.

-=GE=-

Since the original G4 PowerBook Titanium which I bought in 2001, they have ALWAYS run hot when playing games or using the GPU. It's never caused ANY other game or program I've ever used to slow down or caused the processor to change its FRICKING CLOCK-SPEED! If you set your Energy Saver preferences to "Performance" then you will be fine. Not to mention that it doesn't do this exact same freezing and crap when running under Windows XP or Vista! Also, my CPU is not rising above 62C or so at the most, usually it's at 54C or 55C... and it doesn't make a damn bit of difference to my FPS. My fans are running at 5990 RPM (6000 is max).

Meanwhile secondlife is stuck in semaphore_wait_signal_trap loops (if you sample process during the freezes using the Activity Monitor) due to WHATEVER the hell this problem is!!! This is ridiculous!!! Doesn't matter if I set my graphics memory to 128, or 96.. doesn't matter if I "Run Multiple Threads" or not... only thing that helps is running it in Windows!!

Apple or LL or both have to bear some responsibility and compensate us for this, not to mention fixing the problem.

slower??
A Universal binary is made up of at least two totally independent executables, which can't interfere with each other.

The true problem is LL's laziness and negligence.

slower??
A Universal binary is made up of at least two totally independent executables, which can't interfere with each other.

The true problem is LL's laziness and negligence.