random freezeups and crashes

ok whats with this.. the last three clients have been giveing me random freezups and gui lockups?

every so often...mebbie every 4 or 5 minutes the new and improved (yea right) SL client locks up my gui for a few random seconds, when it recovers my cpu is maxed out for 1 or 2 seconds, please don't blame my hardware its only 3 months old and top of the line, i know that it's not the case. i have 2 gigs of ddr2 so thats not the issue, i have a amd 64 x2 @ 2.80GHZ so i know thats not the issue, and i have an nvidia 7600 GS with 512mb ddr2 so i know that my video card isen't the issue, can anyone give me some real answers?

i use ubuntu linux nothing specal vannella install, compiz-cube, i even tryed disableing compiz cube and still the same thing random freezeups and crashes, rare but sometimes i even have to do a hard reset. this is supposed to be a better client, then why are my FPS crap why does it crash when it wants to? why does it not use my usb mic when it detects it?
i might use linux but im no guru, i just know that this should work.

my personal thoughts is that LL screwd up again...instead of working on actually problems they opted for more eyecandy and useless features than stability of client. i could be totally wrong but with the issues im haveing it seems that they have taken a step backwards or 3.

if there is anyone that can help with the issues im experianceing please let me know.

thank you for your time.

Linux is free software, which implicates it's also mostly software availiable on an 'as is'-basis. Lindenlab software for SecondLife(TM) usable with linux is also beta and under (heavvy) development. Best check SL DEV(TM?) on the web for that.

Crashing is self-protection of the system ( like .. 'Nope .. not doing that.. Stopping / Starting over.. ). The system does not 'want to'.. but is given is given many, many opportunities in an environment that is so dynamic as SecondLife(TM) and it's viewer, with VFS, seperate database-servers and so forth , is.

There are no guarantees, the JIRA should be used to adress technical issues, and i'd first make sure that your computer works flawlessly with other 3D applications ( but that's personal ) , before going in-depth into tweaking your SecondLife(TM)-viewer. For instance : I have no more shader problems on my NVidia - board in SL ( <-- OMG I forgot one here, now what.. ? ) since i disabled the VBO in the Advanced Graphic options, but the price is lower frame-rates and i still crash irregularly as any other user.

You cannot use / watch Quicktime(TM)-movies in the SecondLife(TM)-viewer.

FPS is also dependent on the performance of the SIM - server you are presently at. See it with CTRL+SHFT+1. SIM performance can be seen by opening 'Simulation' inside the dashboard appearing on the upper right. There is also a known problem called 'the memory leak' that is mentioned on all operating systems.

And ofc those nearest to the SecondLife(TM)-network will always experience best performance contrast those dangling out the outer rims of the net.

Voice implementation is a seperate discussion in this forum.

Good luck.

that actually diden't answer my question... and none of my other state of the art games do this sort of thing to my computer.... now.. can some one give a real answer as to why this is happning? i know for a 100% fact that it is not my computer. i have 2 gigs of ddr 2 500gb sata 2 hard drive an amd 64 x2 @ 2.80ghz with an nvidia geforce 7600 with 512mb of video ram.. i used envy to install the latest nvidia drivers and still i get random "temp frezeups" now can someone who isen't interested in blaming the linux os or ubuntu please help me? i would like a real answer not a finger pointing fight.

thank you for your time.

This seems similar to an issue that i identified but that should *not* be able to occur on the official linden client only on my debian packages.

Can you look at the debug console when you are running the viewer, or start the viewer from a terminal window so you get the debug output. Right when the viewer stalls look for a message to be printed after it resumes.

I *think* the issue is related to CAPS packets, in my case it was specifically blocking DNS queries. The linden official version uses libcurl linked against libcares and libssl, and this *should* provide asyncronous DNS queries. The debian version of libcurl is linked against libresolve and that will block untill DNS has returned.

One thing you could try to see if it is DNS is install a cacheing DNS server, very easy.... apt-get install bind9.... edit /etc/resolve.conf... write down or back up what it says!..... change the nameserver line to be "nameserver127.0.0.1". run the viewer. This will send all queries through your local caching bind service which will be *way* faster that remote on the internet and it will remember queries.

I have seen a few issues like this on linux and even windows but it *should not* be what i think it is. But i am very interested to find out for sure.

Regards

M2

One thing you might want to check is to see if your system is up to date. A while back I had a horrible problem with stability that I traced to a bad X.org. I researched the problem and found an update package I was able to use until the problem was fixed with an official OpenSUSE update.

Another thing to look into: I've heard stuff from someone who found that his/her power supply just wasn't beefy enough to provide the graphics card with enough power to satisfy the demands of the sl viewer. A power supply upgrade fixed that problem.

Sorry I can't offer more ideas. The only real problems I'm having are the same ones everyone is having: sl's eternal routing, isp, etc. stuff.

For voice issues, I put together a detailed procedure to make that work:
http://www.adamascarter.com/extras/sl_voice_linux.txt

This is written from the viewpoint of OpenSUSE 10.3 running KDE 3.5. Just so you know, if you use Gnome or some other desktop, you'll need to translate.

Video (quicktime) requires gstreamer with quicktime codecs. I have not been entirely successful in getting all video to work properly, but I keep hoping the next gstreamer update gives me what I need!

Adamas Carter