|
|
|
Shifting this to "Critical". The crashing issue is still a huge deal, but it doesn't appear to happen for all operating systems.
Symptoms described above persist in 1.20RC5.
 Please attach the file Application Data/SecondLife/logs/SecondLifeCrasReport.log (I forget the precise Vista location, it would be under Documents and Settings/User in Windows XP) and I'll try running the crash through our crash reporter by hand.
Thanks! The Vista location (just for future reference) is C:\Users\UserName\AppData\Roaming\SecondLife\logs, and AppData is a hidden directory...
Thank you for looking at this! So, we haven't been able to repro this so far. The error suggests that the installed default settings file (e.g. C:\Program Files\SecondLifeReleaseCandidate\app_settings\settings.xml) is missing an entry for "AllowTapTapHoldRun" or is otherwise corrupted such that it isn't parsing completely.
You might want to tray a complete uninstall then a reinstall. If it still crashes, attach the crash file immediately after crashing and include the exact repro. Thanks, This is exactly what I did:
1. Uninstall the RC5 (this leaves only the current 1.19 viewer installed, and that hasn't been touched today). When asked if I wanted files and directories removed, choose "Yes". 2. Install 1.20RC5. 3. When asked if I would like to run Second Life, choose "Yes". 4. Log in and poke around for a few minutes. 5. Log out. Wait a couple minutes. 6. Try to run 1.20RC5 again. The viewer tries to load, but fails after the "Loading Second Life..." box appears. 7. Upload the following files to the ticket: I left the original Crash Report in case you wanted it for comparison. The date of attachment should suffice to tell which is which. If there's something I'm missing, I'd appreciate knowing... Thanks again for looking at this. This is the crash report for 1.20RC6.
I've got the same problem with 1.20RC6, with the same steps. I've attached a Crash Report.
Same steps as before, same result with 1.20RC7.
I've attached the Crash Report to the list... I followed the same steps for 1.20RC8 (just released), and I get the same results. I've attached a Crash Report from the logs directory.
I really hope that the 1.20 release, when it's finally made, doesn't have this problem... There's been a rather interesting turn of events with regard to this issue: I have an account on my computer for my spouse to use, and I noticed the SL Release Candidate icon on the desktop.
For giggles, I clicked it, expecting the usual crash... ...but it WORKED! So I guess my question is this: What would the client be referring to that would be different between these two accounts on the same computer? If I had an answer to that (and how to fix any disparities), I think we'd be well on our way to closing this ticket.... Any assistance would be greatly appreciated! There could be any of a number of things different, but the most likely is some setting in C:\Users\UserName\AppData\Roaming\SecondLife\user_settings\settings_releasecandidate.xml (or possibly settings.xml in the same folder).
The best plan of action would be to move this file out of the way and see if it still crashes on startup. If it doesn't crash, could you upload the settings file so we can see what made the difference? I couldn't get 1.20RC8 to load again after renaming settings_releasecandidate.xml (or settings.xml for that matter), so I uninstalled 1.19 and 1.20. I then removed the whole SecondLife folder in C:\Users\UserName\AppData\Roaming before installing 1.20RC9. (I wanted to make sure that there were no issues at all between the standard 1.19 viewer and the release candidate.)
So far, 1.20RC9 behaves like all other RC versions since 1.20RC2: re-entering the RC viewer after installing and exiting the program results in crashing right after the "Loading Second Life" box appears. I just downloaded 1.20RC10 and installed it. While it ran, I was very impressed.
When I quit the program and tried to re-run it, I found the problem persisting. Crash Report Log is attached. It's worth noting that I've tried running the Release Candidate with and without the settings files, with the same results. I'm not sure why this is happening. I had to re-install my operating system (debugging a hardware problem and HP Level 1 support can't grok using a Linux LiveCD to diagnose something like that), and when I tried 1.20RC10 on a fresh install, it worked like a champ.
This tells me that it wasn't necesarily an OS issue, nor was it (necessarily) a problem with the RC, but more something in how my user account was configured. Sigh. I have no idea what that difference would be. Is this now delegated to the realm of "non-issue"? Hi,
are you running as administrator or user? we've heard that some folks are having issues when running as user. You know Alexa, I'm not sure. I'm running as the first user it makes when the Vista OS is installed. I have the bits enabled that cause the OS to ask me if I want to use Admin rights to do some things (like install SL).
I noticed with the latest RC (11) that right after "Detecting Hardware" was "Initializing texture cache". I'm wondering now, if there wasn't some property of the directory that got munged, causing the program to crash due to lack of permissions or something? This would have been resolved through a reinstallation of the OS... At this point I'm guessing, because the RC is working and I don't have the slightest idea what would have caused the failure to begin with. |
|||||||||||||||||||||||||||||||||||||||||||||||||
 |
|
Bug
Resolved
Critical
Release Candidate crashes BEFORE login screen
The information:
CPU: Intel(R) Core(TM)2 CPU T5200 @ 1.60GHz
Memory: 2025 MB
OS Version: Linux 2.6.24-16-generic #1 SMP Thu Apr 10 13:23:42 UTC 2008 i686
Graphics Card Vendor: NVIDIA Corporation
Graphics Card: GeForce Go 7600/PCI/SSE2
OpenGL Version: 2.1.2 NVIDIA 169.12
LLMozLib Version: [LLMediaImplLLMozLib] - 2.01.14688 (Mozilla GRE version 1.8.1.13_0000000000)