Interesting Crashing Issues

Any idea why this happens... in the new client 1.20, when i put the machine in a locked state with the client running it seems to cause it to not respond and force quit ive tried several options using Vista and nothing has worked thus far, any ideas?

Are you referring to the user account-based "lock workstation", like you might find in Windows Server 2003/200x? (I don't have Vista)
If you are, is it only the 1.20 viewer, or does the 1.19.x viewers do it too?
Have you checked to see if locking the system has an immediate effect on SL? (lock it, and then unlock it right away and see if SL chokes). If SL goes unresponsive right away, I'd have to think something in the lock process is releasing resources needed by SL, causing it to go into a limbo disconnect. Applications are supposed to stay running, so that is really odd.
If you CAN lock and unlock and SL is ok, but SL chokes if you lock it and leave it that way for a little while, I would think your power savings settings are dropping you into standby mode, which WOULD disconnect you from the net and put running programs on the back burner.

I can tell you that I have walked away from the computer and it has gone into automatic lock mode because I have not returned soon enough -- windows account login, that is. I have no issues when I return, unlock the computer and continue with SL. However, I run XP Pro and I seldom ever run with the 1.20 client, so one or both of those may have something to do with me having no problems.

I was wondering the same thing, but with a slight twist: When my Linux box goes into screensaver mode, it will sometimes crash SL, presumably because of some unholy interaction in OpenGL. Granted, this is very far from Vista, but it would be helpful to know if just locking and immediately unlocking the Vista box causes this problem for the OP, or if both the locking and the crash are products of something else, from an OS idle timer.

Yeah, OpenGL screensavers and SL together are teh debil. Had a number of crashes and freezes because the two were fighting for resources. My big issue atm is from Outlook Express in WinXP. Sometimes after checking my email and closing the application, it'll leave the msimn.exe process running. If i run SL with that process running, after the timer for "check messages every X minutes" expires, it robs SL of something it really needs to do that and I get a SL hard crash. Never does it if i close the msimn.exe process before i run SL. There must be a LOT of resource stealing going on with SL, and it makes me wonder if a lot of peoples problems are due to that.