|
|
|
agreed, that is obviously the relevent line in the log, just to be clear, though, this isn't intermittent, like high lag or something, it always crashes there prior to the SL window appearing.
Still happening with the new 1.18.4 release of 11/07/07:
2007-11-08T16:25:52Z INFO: LLViewerImageList::doPreloadImages: Preloading images... New to Second Life and I am outta here! What a buggy program. I connect., it runs for 30 seconds and freezes. Lotsa fun!!!!!!!!!
As a newbee to Second Life I experienced crashing every time I logged in. Now finding all these complaints about this issue, my resolution is to uninstall...permanently.
Still happening with the 1.18.5 release of 11/13/07. Log file shows the same last lines:
2007-11-14T03:34:57Z INFO: LLViewerImageList::doPreloadImages: Preloading images... Is this still happening? The only thing that can cause this is a bad install. Check the following file:
c:/Program Files/SecondLifeReleaseCandidate/skins/textures/ There should be an entry at the very bottom for: lag_status_critical.tga If there -Steve There is neither a lag_status_critical.tga entry in textures.xml nor a lag_status_critical.tga file in this directory. I have done a complete wipe and reinstall several times.
This problem is due to a bug in the installer - neither the installer or the uninstaller are aware of the changes to the Vista filesystem related to User Account Control (UAC), specifically the VirtualStore, and do not clear out the user's AppData\Local\VirtualStore\Program Files\SecondLifeReleaseCandidate directory. All reinstalls fail because old versions of the file are used instead.
The right thing to do would be to make the installed Vista compatible, the workaround is to manually delete Second Life files from the VirtualStore as well as from the standard Program Files location. Turning off User Account Control during installation might also solve the problem, but I didn't test that. I am running into the same issue. Every time I try to use this viewer it goes straight to crash logger... whether I file one or not, SL never opens. I have removed and reinstalled 3 times with the exact same results.
I'm getting the same thing. This is not restricted to Windows.
i'm getting this problem every time I do a cache clearing on my SL viewer. Hardware Overview: Machine Name: iMac GeForce FX 5200: Chipset Model: GeForce FX 5200 I'm getting the same problem on Windows XP SP2.
By the way, an older version of SL ran perfectly on my computer. At one point in time, I could no longer use it and was asked to update; I then haven't played for a while and now I was trying to start the program (downloaded on Wed, Nov 14), and it never worked despite of several reinstallations, cache cleaning and all that stuff. Might there be a software incompatibility problem? Hope this is solved soon!!! ~Amalia This has also affected Mac systems as well. I am currently on a MBP - tried to log in with the Windlight viewer that was working very well on friday - today I crashed on log in using the Windlight viewer. When I tried to log with the latest regular client - it crashed during start up ... didn't get the sl login screen at all! Now any version of the client I try is crashing on start up.
Hardware Overview: Model Name: MacBook Pro 15" ATI Radeon X1600: Chipset Model: ATY,RadeonX1600 Using Vista op system, was working fine until I downloaded the brand new version promoted on the sign in screen last evening. Now goes straight into the error reporting system ... no sign on screen, nothing. Ridiculous buggy program. I'm ready to bail.
i seems to have the same problem...crashing right after the little dialoge box that says detecting hardware and then right to crash message....but..in my logs i cant find the "relevant" line ..but i cannot find this lag_status_critical.tga file in my textures folder..for wot i read in the file textures.xml( lag_status_critical.tga value="e2c74120-e896-4952-bf9f-d70696e712a7" ) lag_status_critical.tga should be named e2c74120-e896-4952-bf9f-d70696e712a7.tga but theres not such file ...so i dont know what to do...i have windows vista and i had never run SL for first time...im a newb at the game..but i havent been able to try it out.....anyway heres my log....plz take a few mins and read it....:
2007-11-19T20:25:58Z INFO: another_instance_running: Checking marker file for lock... Vendor: AuthenticAMD // CPU Configuration // CPU Extensions 2007-11-19T20:25:58Z INFO: write_system_info: Memory info: 2007-11-19T20:25:58Z INFO: write_system_info: OS info: Microsoft Windows Vista (Build 6000) Any help PLZ hey i wanted to edit something of my last post I DO HAVE THE FILE lag_status_critical.tga that is named e2c74120-e896-4952-bf9f-d70696e712a7.tga like it says on textures.xml ...thats why my logs doesnt show that line...but...again..why does it crash ?
by the way...i cannot send crash report..it freezes on trasmiting data for ever :S
I am just adding in my info... I also crash immediately upon login.
OS: Microsoft Windows Vista (Build 6000) Processor AMD Athlon 64 X2 Dual Core Processor 4200+ This is for the Windlight Viewer 1.18.5 I was having the immediate crash upon getting to the login screen (it'd show for a fraction of a second and then die). Not sure the same issue was causing the crash. I'd installed, reinstalled, reinstalled my drivers, and nothing had worked. I read somewhere around here that someone suspected that the game isn't installing/uninstalling correctly, so I tried deleting all folders with any reference to "second life" or "linden" as well as all registry keys matching that same pattern.
Now, here's where my process got dirty. Instead of testing immediately, I did other stuff. I started thinking about the problems I'd had with Windlight and things I could try to get that to work and why my video card was misreporting its memory and all that... (long story short I started messing with ATI Tray Tools and didn't keep track of what I did) So I guess I can't really confirm for sure that clearing out the files and registry keys is what helped, basically. But give it a shot. If some people can get this to work, then that gets an issue with SL's installer exposed. Off topic, I'm going to mess with overriding the shaders to a lower version (function of ATI Tray Tools) to see if I can get water to look like it's supposed to in Windlight. Thought I'd throw it out there to share the idea. I should probably clarify that this was happening to me in the RC, Windlight, and the current main release, and that I've only just gotten the Windlight login screen up and haven't tried anything else yet. Just wanted to establish that there was some effect to something I did.
If you have this bug and if you are willing to try a 3rd party viewer, please go to If so, you should get crash dumps and a message pointing to instructiions on Good Morning, for the last hour (0830 to 0930 PST) I have tried to log in. The system will start and then go right to the crash logger screen. I tried another laptop and had the same results. The program worked fine last night, 11-29-07, on both machines. Since upgrading to Windlight, I have had only one instance where there was a possible problem: the screen would start flashing muti colors, settle down, then freeze up. If I wait one to two minutes, it clears for an equal time then freezes up totaly.
Hi Nicholaz, in my case, the problem was caused by bugs in the installer, which I suspect may be the case for a lot of these people. Your viewer did seem to handle the problem better, although whether that's because of your error handling being better or because your last build (I'm not sure if there's a new one) was based on a build of the viewer before the changes in textures.xml that caused the later viewers to crash if they encountered an older version of the file than they expected.
In any case, it's hard to say whether these issues should be fixed in the viewer or the installer or both. But, I'm fairly certain that a lot of them are caused by bad installs and the fact that the installer does not reinstall properly over older files in the various directories it uses that the user probably won't be aware of and on the Mac and Windows, might even be hidden from them (such as the Vista VirtualStore directories). Emma, In your case it's definitely clear. If the viewer emits an ERROR entry to the log, the viewer definitely closes (in all installs/version). Something tagged ERROR is internally considered a situation from which they can't recover (and it usually points (in developer's cryptic ways) to the cause of the error). It looks like a crash, but actually the viewer is pulling the plug. If the log ends with anything else (INFO/WARNING) the viewer really crashed and very often the crash has nothing to do with what is visible at the end of the file. Problem for me started with 1.18.6 RC0. The viewer displays the login screen then it crashes (even if I don't type my password or I don't do anything) and doesn't report crash as it can't find servers. An important detail could be that the viewer does not display version number correctly in the lower right corner. All is OK with 1.18.5 (3) viewer.
i am seeing a new crash with 1.18.6.0 that I have not had on previous versions. I already apply a number of patches to my builds that catch a number of possible crashes (following Nicholaz's work) but I am seeing crashes in random places in the code at random times. I have started gathering back traces but as yet there is no pattern. I would guess there is some object management issue crept in causing possibly wild pointers somewhere.
The problem is more pronounced when i move around a lot. If i stay in one area working on scripts (for example) I can last a long time but frequent movement and therefor lots of object changes and texture changes seems to trigger the crash more often. When i have gathered some more Bt's i will drop them here or sldev for others to take a peek and see if they can get a clue what is happening I've also just noticed this bug was related to crash at startup. So my above info is probably not relevant to this bug, but it might be :- I have had some crashes at startup but 98% of the time late on.
tried 1.18.6 RC1 and having exactly same issue, nothing changed.
Tried 1.18.6 windilght first look and still having the same issue. It seems it does not find correct DNS or a way to reach servers... possible?
I cannot log in for 2 days now.. during Xmas... great timing.. it starts to load and then crashes, and also alternatively I get an error message saying the region has started the log out process and then crashes... so frustrating.. My husband can log in from the same computer... NO ISSUES// but I crash each and every time.... bottom line.. I cannot log in???
diamonds: try deleting your settings from the application data folder. If it works for another user on the PC, maybe starting with fresh settings helps (Windows-search (F3) for a folder named diamonds_beaumont containing a settings.xml)
Tried 1.18.6 RC2, now the version number is correctly displayed, the images come up on the login screen then, after a few seconds, viewer still crashes by itself. Crash cannot still be reported as it says "cannot find servers". When I start the official 1.18.5(3)
/me humbly suggests that a few different problems are being mixed under this JIRA entry.
The original post from gigs suggested a problem with "lag_status_critical.tga" Other posts are concentrating on DNS problems. Other posts such as Kreig's may indicate a Vista or Graphics driver problem since the log doesn't show anything much. Still more problems can be caused by incorrect firewall settings. I'm not suggesting it will cure any of your problems, but I hope people are checking the support pages and ensuring the right ports are clear for SL. Since the original log posted and the first comment concern "lag_status_critical.tga" errors, can I suggest the issue be renamed and the description changed to reflect this? (Merry Christmas!) Tried 1.18.6 RC3, still crashing at startup while 1.18.5(3) working.
And Fluff, I perfectly agree with you, this entry is a mess, but I am not a tech nor a bug hunter and if I knew WHY I am having such problems probably It would be a much better start. I actually can 't say WHY this candidate release crashes in my system, and I think it's not my work to do it (as I am not able to). I simply ask a program to work when I install it. Linux client, just installed today, from distribution supplied package.
Crashes with cannot create window error. I have not once, in 6 months, been able to get into the community since the client ALWAYS has crashed with the same error. I got the same problem on one computer. Running Vista and Nvidia 7900 GS. I was actually able to get SL to run once. I reinstalled and then went into the Nvidia control panel and checked Allow the application to determine the graphics settings. SL loded and ran one time. After closing and restarting it went back to Crash logger after detecting hardware. Ok windlight did the same thing. But listen to this....the On Rez viewer works everytime. Go grab the On Rez viewer and you can get in.
Ok after a bit more testing I got the recurrent crash logger to finally let me log in. Here is what I did. I had resently tried the OnRez viewer and it could log on without that crash logger coming up everytime and stopping me. So I copied all the files from it into the Secondlife folder and of course it worked fine....Until I renamed the OnRez viewer SeecondLife. Ah hah! So my computer will crash when it sees Secondlife is about to run and be ok when OnRez runs even if it is the exact same program? Ok seems so. I then got a clean instal of SecondLife and renamed the EXE to SecondLife_BAK and clicked it. Guess what?... it works. Ok so somewhere in windows secondLife has a file that told the crash loggerr that it was crashed and it never cleared that out. I think the crash logger then may be suspect. Also I think this all started because I used my own graphics settings instead of letting the application decide. So it crashed then kept that state and never would change it even when I reinstalled. So changing the name of SL was all that was needed to get around that. The problem is that when SL crashes again is the new name then going to be flagged as a crash everytime it is run?
Anyways my machine is a p4 duo,Vista Home,Nvidia 7900 GS ...updates and such for windows and nVdia card had zero effect and this problem has been reported on Linux as well as XP and Mac. So you guys out in San Fran please look back and see what was changed in the crash logger recently. Ok I have confirmed with at least one other resident that renaming the SecondLife.exe to something else gets beyond the crash bug on login. Some has said that using a program like CCleaner to clean the registry may work. Is SL corrupting the registry? I dont think my computer specs are any concern because this is happening on all kind of platforms but I think just renaming will eventually fail also as it will need to be renamed again after some crashes...so I dunno.
Same problem. Attempt at starting SL goes straight to crash reporting – no login screen. This first occurred on 19 January 2008. Before that I was using the same version of SL on the same computer for months. Could it be that an incompatability has been caused by an update on some other application, such as Symantec, which is blocking SL login? I can get into SL by downloading and then choosing run after download is completed. I have to do that every time I want to play..... Pain in the neck.
Now get the problem with the 1.18.6 version of Windlight and need to reboot to get it to load.
Second Life 1.18.6 (77495) Jan 22 2008 15:30:40 (Second Life WindLight) CPU: Intel Core 2 Series Processor (2393 MHz) Vista users:
Please delete the SecondLife directories (SecondLife, SecondLifeReleaseCandidate, SecondLifeWindlight) found inside the Vista VirtualStore and reinstall. The VirtualStore is inside your user directory inside the hidden AppData folder. C:\Users\yourusername\AppData\Local\VirtualStore\Program Files\ Substitute your windows username for the "yourusername" in the above path and copy it into Windows Explorer. The Second Life installer does not appear to clear these out correctly and when it launches in tries to use the old files that are in these directories, resulting in a crash. Emma Nowhere's suggestion doesn't work – there are no SecondLife directories in the Virtual Store.
Since this terrible bug is still here with the last 1.19 viewers, people who manages to understand my poor english can try this workaround that works for me under vista :
In device manager select your graphic card (right click) and then choose "properties", then the "driver" tab, then "update driver", then "choose a driver on my computer" (do not let windows search automatically), then click "let me choose a driver manually" then select again your last driver on the list, (no need to choose another driver, same one is ok), ) and then click « next »... when finished, cross your fingers and try to lanch the SL viewer... Despite boring, this works 100% on my computer ...BUT for some reason, only until next computer restart... im trying to get on the game and it Crashes on me as soon as i get in ...and as in playing the game ... now i can even get in the game can you help me
thanks tina |
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
 |
|
Bug
Resolved
Showstopper
Crashes on startup
2007-11-02T17:21:39Z llxml/llcontrol.cpp(294) : error
2007-11-02T17:21:39Z ERROR: LLControlGroup::getString: Invalid string control lag_status_critical.tga