Whirly Fizzle commented at 2014-11-11T19:28:51Z

Heya LilithStClair,

You are on an older version of the viewer there.

Please can you update to the latest version from https://secondlife.com/support/downloads/ and see if this fixes your problem.

Theres been quite a few people having this problem with the login fields not appearing. They all have one thing in common and that is they are using an old version of the viewer.
Not sure of the cause but I suspect they all got a viewer update to a version using the new login screen layout but they are launching an older version of the viewer from an old desktop shortcut, which is breaking the login page (because of saved settings made from the newer version).

Please comment back if the latest release works okay for you.

LilithStClair commented at 2014-11-11T21:21:55Z

Hi,

I have updated my viewer and not it won't open at all. It goes as far as Initializing VFS and then nothing happens. The viewer just doesn't open.

Whirly Fizzle commented at 2014-11-11T21:28:21Z

Ahh damn - yes a few people have reported this problem too - see BUG-7776

Does the viewer just stay stuck on "initialising VFS..." or does the viewer actually crash and close to desktop?

Can you try the following first when using the updated viewer:

• Make sure hidden files and folders are set to show on Windows - see Option 1 on http://www.sevenforums.com/tutorials/394-hidden-files-folders-show-hide.html
• Browse to C:\Users\ [USERNAME] \AppData\Local\
• Inside this Local folder, you will see a folder named "SecondLife"
• Delete the whole SecondLife folder.
• Launch the default release viewer (http://wiki.secondlife.com/wiki/Release_Notes/Second_Life_Release/3.7.20.296094) and see if the problem is fixed.

If this does not work, launch the 3.7.20.296094 viewer and let it crash/get stuck
Then zip up your logs folder and attach it to this issue using More Actions -> Attach files.
This page tells you where to find the logs folder: http://community.secondlife.com/t5/English-Knowledge-Base/How-to-report-a-bug/ta-p/733545#Section_.3

I'm hoping that if the viewer is just stuck at initilaising VFS and not actually crashing that the manual cache clear should fix it.

LilithStClair commented at 2014-11-11T21:50:24Z

Tried deleting the folder, but still nothing. The viewer doesn't get stuck, it just crashes, I tried re-installing it but the same thing happened. It only started after I updated my viewer. I even went back to Firestorm and Singularity, but hate both of them lol.

Whirly Fizzle commented at 2014-11-11T21:53:33Z

Lilith, please can you let the Linden viewer crash and then attach your viewer log files

Zip up your logs folder and attach it to this issue using More Actions -> Attach files.
This page tells you where to find the logs folder: http://community.secondlife.com/t5/English-Knowledge-Base/How-to-report-a-bug/ta-p/733545#Section_.3

LilithStClair commented at 2014-11-11T22:12:27Z

Hope I have sent the right files :)

Whirly Fizzle commented at 2014-11-11T22:21:26Z

Nearly!

The log session in SecondLifeCrashReport.log shows the crash here....

2014-11-11T21:45:48Z INFO: LLFeatureManager::parseFeatureTable: Attempting to parse feature table from C:\Program Files (x86)\SecondLifeViewer\featuretable.txt
2014-11-11T21:45:48Z INFO: LLShaderMgr::dumpObjectLog: From Benchmark Shader:
2014-11-11T21:45:48Z INFO: LLShaderMgr::dumpObjectLog: No errors.

2014-11-11T21:45:49Z INFO: windows_post_minidump_callback: Dump file was generated.
2014-11-11T21:45:49Z INFO: windows_post_minidump_callback: generated minidump: C:\Users\Lucy\AppData\Roaming\SecondLife\logs\dump-c49a18c5-57a1-b0fd-0c5a-6c110f149df7\400ff80d-72f8-43fa-bf8d-b53861fe3e79.dmp
2014-11-11T21:45:49Z INFO: windows_post_minidump_callback: Entering Windows Exception Handler...
2014-11-11T21:45:49Z INFO: LLAppViewer::handleViewerCrash: Handle viewer crash entry.
2014-11-11T21:45:49Z INFO: LLAppViewer::handleViewerCrash: Last render pool type: 0

Comparing that to my own logs on the benchmark viewer, you seem to crash right before the "gpu_benchmark: Memory bandwidth" should be printed to log.
"Last render pool type: 0" This usually shows a "0" when the problem is graphics or driver related too.

There should be more files in the viewer Logs folder, including a subfolder/s named something like "dump-c49a18c5-57a1-b0fd-0c5a-6c110f149df7"

Can you go to C:\Users\ [USERNAME] \AppData\Roaming\SecondLife
Find the folder named Logs
Right click the Logs folder -> Send to -> Compressed (zipped) folder.
Attach that Logs.zip folder to this issue.

LilithStClair commented at 2014-11-11T22:26:09Z

Hopefully got that right this time lol

Whirly Fizzle commented at 2014-11-11T22:26:40Z

Perfect!

LilithStClair commented at 2014-11-11T22:30:07Z

yay...finally lol

Whirly Fizzle commented at 2014-11-11T22:36:35Z

Gosh, lots of dumps in those logs.

Callstack:

Operating system: Windows NT
                  6.1.7601 Service Pack 1
CPU: x86
     GenuineIntel family 6 model 42 stepping 7
     4 CPUs

Crash reason:  EXCEPTION_ACCESS_VIOLATION_EXEC
Crash address: 0x0
Assertion: Unknown assertion type 0x00000000

Thread 0 (crashed)
 0  0x0
    eip = 0x00000000   esp = 0x00b3df30   ebp = 0x00b3df54   ebx = 0x00000000
    esi = 0x02caa5d0   edi = 0xffffffff   eax = 0x00b3df4c   ecx = 0x00000002
    edx = 0x00000001   efl = 0x00010202
    Found by: given as instruction pointer in context
 1  SecondLifeViewer.exe!LLGLSLShader::stopProfile(unsigned int,unsigned int) [llglslshader.cpp : 219 + 0x12]
    eip = 0x01bdbf0f   esp = 0x00b3df5c   ebp = 0x00b3df64
    Found by: previous frame's frame pointer
 2  SecondLifeViewer.exe!LLVertexBuffer::drawArrays(unsigned int,unsigned int,unsigned int) [llvertexbuffer.cpp : 848 + 0x9]
    eip = 0x01bce544   esp = 0x00b3df6c   ebp = 0x00b3dfb0
    Found by: call frame info
 3  SecondLifeViewer.exe!gpu_benchmark() [llglsandbox.cpp : 986 + 0x10]
    eip = 0x01317487   esp = 0x00b3dfb8   ebp = 0x00b3e94c
    Found by: call frame info
 4  SecondLifeViewer.exe!LLFeatureManager::loadGPUClass() [llfeaturemanager.cpp : 425 + 0x4]
    eip = 0x0111e081   esp = 0x00b3e954   ebp = 0x00b3e990
    Found by: call frame info
 5  SecondLifeViewer.exe!LLFeatureManager::init() [llfeaturemanager.cpp : 783 + 0x6]
    eip = 0x01122d8f   esp = 0x00b3e998   ebp = 0x00b3ec00
    Found by: call frame info
 6  SecondLifeViewer.exe!LLViewerWindow::LLViewerWindow(LLViewerWindow::Params const &) [llviewerwindow.cpp : 1736 + 0xb]
    eip = 0x0183a756   esp = 0x00b3e9a0   ebp = 0x00b3ec00
    Found by: call frame info
 7  SecondLifeViewer.exe!LLAppViewer::initWindow() [llappviewer.cpp : 3167 + 0x28]
    eip = 0x00fe0b0d   esp = 0x00b3ec08   ebp = 0x00b3edbc
    Found by: call frame info
 8  SecondLifeViewer.exe!LLAppViewer::init() [llappviewer.cpp : 1002 + 0x8]
    eip = 0x00ff0e34   esp = 0x00b3edc4   ebp = 0x00b3fb7c
    Found by: call frame info
 9  SecondLifeViewer.exe!WinMain [llappviewerwin32.cpp : 278 + 0x8]
    eip = 0x0193237f   esp = 0x00b3fb84   ebp = 0x00b3fbb8
    Found by: call frame info
10  SecondLifeViewer.exe!__tmainCRTStartup [crtexe.c : 547 + 0x1b]
    eip = 0x022c9189   esp = 0x00b3fbc0   ebp = 0x00b3fc4c
    Found by: call frame info
11  kernel32.dll + 0x13389
    eip = 0x7767338a   esp = 0x00b3fc54   ebp = 0x00b3fc58
    Found by: call frame info
12  ntdll.dll + 0x39f71
    eip = 0x77ba9f72   esp = 0x00b3fc60   ebp = 0x00b3fc98
    Found by: previous frame's frame pointer
13  ntdll.dll + 0x39f44
    eip = 0x77ba9f45   esp = 0x00b3fca0   ebp = 0x00b3fcb0
    Found by: previous frame's frame pointer

LilithStClair commented at 2014-11-11T22:38:49Z

yeah, i have been having a few issues in last couple of days O.O

Whirly Fizzle commented at 2014-11-11T22:46:15Z

Checked a few of the .dmps out of the many and they all have the same stack so far.
Attached a full stack as Callstack.txt

Lilith it looks like somethings going really wrong here with the Benchmark viewer changes, a Linden will need to tell you what to do next.

Only thing I can suggest trying is updating your graphics driver to the latest version and see if this fixes the problem - I have no idea if it will help, but you are on a fairly old driver version (8.15.0010.2476)

You can run the Intel driver update utility from http://www.intel.com/p/en_US/support/detect?iid=dc_iduu to get the latest driver for your card.

If that doesnt help, you can roll back to an older version of the viewer without the benchmark changes and disable autoupdates.

Whirly Fizzle commented at 2014-11-11T22:51:41Z

Oh wait... I just noticed something else...

static_debug_info.log shows...

    <key>OSInfo</key>
        <string>Microsoft Windows XP </string>

... but you are using Windows 7

Can you check something...

Right click the desktop shortcut for the crashing Linden viewer -> Properties -> Compatibility tab
Is "Run this program in compatibility mode for...." ticked and set to Windows XP?
If it is ticked, untick it.
Nothing at all should be ticked under that compatibility tab.
Apply changes -> save and launch the viewer and see if it still crashes.

Whirly Fizzle commented at 2014-11-11T22:54:32Z, updated at 2014-11-11T23:04:59Z

Aha!
secondlife.log also thinks you are using XP

2014-11-10T21:47:19Z INFO: LLAppViewer::writeSystemInfo: OS: Microsoft Windows XP 
2014-11-10T21:47:19Z INFO: LLAppViewer::writeSystemInfo: OS info: Microsoft Windows XP Service Pack 2 (Build 2600) compatibility mode. real ver: 6.1 (Build 7601)

Not all sessions on the Benchmark viewer show as running on XP though.
I suspect you may have tried changing compatibility mode as a workaround for the crash.

LilithStClair commented at 2014-11-11T23:14:12Z

nothing was ticked under compatibility, i didn't even know you could change it lol

LilithStClair commented at 2014-11-11T23:49:28Z

right, i have used the Intel link and updated everything...but still the same problem

Whirly Fizzle commented at 2014-11-12T02:22:11Z

Ach well, it was worth a try.

One last suggestion - try deleting the viewer settings folder and see if you still crash on login.
I don't think it's going to help tbh but worth a shot.

Browse to C:\Users\ [USERNAME] \AppData\Roaming
Delete the whole SecondLife folder
Launch the viewer and see if you crash.

Warning: Your chat logs are stored within this SecondLife folder, so back them up if you wish to keep them.
You can just rename the SecondLife folder to SecondLife_old instead of deleting it to test. Then if it doesnt work, delete the new SecondLife folder created and rename SecondLife_old back to SecondLife.

Whirly Fizzle commented at 2014-11-12T03:50:17Z

If that doesnt help, try the Attachments-RC viewer from http://wiki.secondlife.com/wiki/Release_Notes/Second_Life_Release/3.7.20.296355
This one should be okay for you.

LilithStClair commented at 2014-11-12T21:08:03Z

Hi..me again lol
I have downloaded the older version you've suggested and it worked fine for a while but now every time I launch the viewer, it is asking me to update. How can I stop this?
Thanks

Whirly Fizzle commented at 2014-11-13T01:34:25Z

Which viewer version is it trying to update you to?
You need to stay on a viewer version without the benchmark changes until this crash is fixed.

What you can do for now is...
Install a viewer version without the benchmark changes - for example the Attachments-RC from http://wiki.secondlife.com/wiki/Release_Notes/Second_Life_Release/3.7.20.296355 that we know works okay for you.
Right click the desktop shortcut for this viewer version -> Properties -> Shortcut tab
Here you will see a text box named "Target".
Go to the end of the text in this text box and enter a space.
After the space type in ```Java
--channel NoUpdate

Apply and save the changes.
Launch the viewer from this shortcut and the updater will be disabled.

Hope that helps.

LilithStClair commented at 2014-11-13T09:19:57Z

Thank you, that worked a treat for me

Lilith

Whirly Fizzle commented at 2014-11-14T00:42:40Z

Okay great.
I'll leave you a comment once there is a viewer update with a fix for this crash.
Remember that while you have the "--channel NoUpdate" added to the shortcut target path, the updater will not kick in and you wont be informed automatically of any viewer updates.
To enable the updater again once this problem is fixed, you must remove the "--channel NoUpdate" from the shortcut target path.

Marissa Linden commented at 2014-11-14T00:58:36Z

It looks like our benchmark to determine gpu class is crashing old intel gpus. Importing to MAINT.

Alexa Linden commented at 2014-11-18T22:03:13Z

Can you try testing the following build http://automated-builds-secondlife-com.s3.amazonaws.com/hg/repo/oz_maint-4678/rev/296847/index.html and let me know if this resolves your issue?

Whirly Fizzle commented at 2014-11-18T22:26:48Z, updated at 2014-11-18T22:42:00Z

I am unsure if this is expected behaviour or not.

On default release 3.7.20.296094, my system defaults to High Ultra, Class 5

2014-11-18T22:18:04Z INFO: gpu_benchmark: Memory bandwidth is 52.227GB/sec according to CPU timers
2014-11-18T22:18:04Z INFO: gpu_benchmark: Memory bandwidth is 117.191GB/sec according to ARB_timer_query
2014-11-18T22:18:04Z INFO: LLFeatureManager::applyRecommendedSettings: Applying Recommended Features
2014-11-18T22:18:04Z INFO: LLFeatureManager::applyBaseMasks: Setting GPU Class to Class5
2014-11-18T22:18:04Z INFO: LLFeatureManager::maskFeatures: Applying GPU Feature list: Class5
2014-11-18T22:18:04Z INFO: LLFeatureManager::maskFeatures: Applying GPU Feature list: MapBufferRange
2014-11-18T22:18:04Z INFO: LLFeatureManager::maskFeatures: Applying GPU Feature list: VRAMGT512
2014-11-18T22:18:04Z INFO: LLFeatureManager::maskFeatures: Applying GPU Feature list: HighUltra

On the oz_maint-4678 viewer, my system defaults to Mid-High, Class 3

2014-11-18T22:20:38Z INFO: gpu_benchmark: Memory bandwidth is 23.504GB/sec according to CPU timers
2014-11-18T22:20:38Z INFO: gpu_benchmark: Memory bandwidth is 31.024GB/sec according to ARB_timer_query
2014-11-18T22:20:38Z INFO: LLFeatureManager::applyRecommendedSettings: Applying Recommended Features
2014-11-18T22:20:38Z INFO: LLFeatureManager::applyBaseMasks: Setting GPU Class to Class3
2014-11-18T22:20:38Z INFO: LLFeatureManager::maskFeatures: Applying GPU Feature list: Class3
2014-11-18T22:20:38Z INFO: LLFeatureManager::maskFeatures: Applying GPU Feature list: MapBufferRange
2014-11-18T22:20:38Z INFO: LLFeatureManager::maskFeatures: Applying GPU Feature list: VRAMGT512
2014-11-18T22:20:38Z INFO: LLFeatureManager::maskFeatures: Applying GPU Feature list: MidHigh

System Information:

Second Life 3.7.21 (296847) Nov 18 2014 13:09:14 (Second Life Release)
Release Notes

CPU: Intel(R) Core(TM) i7-4770K CPU @ 3.50GHz (3491.92 MHz)
Memory: 16268 MB
OS Version: Microsoft Windows 7 64-bit Service Pack 1 (Build 7601)
Graphics Card Vendor: NVIDIA Corporation
Graphics Card: GeForce GTX 750/PCIe/SSE2

Windows Graphics Driver Version: 9.18.0013.4475
OpenGL Version: 4.4.0 NVIDIA 344.75

libcurl Version: libcurl/7.38.0 OpenSSL/1.0.1h zlib/1.2.8
J2C Decoder Version: KDU v7.0
Audio Driver Version: FMOD Ex 4.44.31
Qt Webkit Version: 4.7.1 (version number hard-coded)
Voice Server Version: Not Connected
Built with MSVC version 1600

Alexa Linden commented at 2014-11-18T23:17:51Z

I've attached 2 images showing the difference between the Release build default settings and the linked fix's default settings. My Graphics driver was updated this afternoon around 1pm

Kyle Linden commented at 2014-11-19T01:00:47Z, updated at 2014-11-19T01:02:55Z

We have one more build we'd like you to try out that addresses the default graphics settings.

http://automated-builds-secondlife-com.s3.amazonaws.com/hg/repo/oz_maint-4678/rev/296857/index.html

Whirly Fizzle commented at 2014-11-19T06:43:49Z

That build defaults me to High-Ultra, class 5, the same as default release 3.7.20.296094

2014-11-19T06:28:42Z INFO: gpu_benchmark: Memory bandwidth is 23.366GB/sec according to CPU timers
2014-11-19T06:28:42Z INFO: gpu_benchmark: Memory bandwidth is 30.092GB/sec according to ARB_timer_query
2014-11-19T06:28:42Z INFO: LLFeatureManager::applyBaseMasks: Setting GPU Class to Class5
2014-11-19T06:28:42Z INFO: LLFeatureManager::maskFeatures: Applying GPU Feature list: Class5
2014-11-19T06:28:42Z INFO: LLFeatureManager::maskFeatures: Applying GPU Feature list: MapBufferRange
2014-11-19T06:28:42Z INFO: LLFeatureManager::maskFeatures: Applying GPU Feature list: VRAMGT512

Second Life 3.7.21 (296857) Nov 18 2014 15:44:08 (Second Life Release)
Release Notes

You are at 115.0, 94.0, 21.8 in Testylvania Sandbox located at sim10620.agni.lindenlab.com (216.82.52.182:13007)
SLURL: http://maps.secondlife.com/secondlife/Testylvania%20Sandbox/115/94/22
(global coordinates 332,659.0, 306,270.0, 21.8)
Second Life Server 14.10.24.295913
Retrieving...

CPU: Intel(R) Core(TM) i7-4770K CPU @ 3.50GHz (3491.94 MHz)
Memory: 16268 MB
OS Version: Microsoft Windows 7 64-bit Service Pack 1 (Build 7601)
Graphics Card Vendor: NVIDIA Corporation
Graphics Card: GeForce GTX 750/PCIe/SSE2

Windows Graphics Driver Version: 9.18.0013.4475
OpenGL Version: 4.4.0 NVIDIA 344.75

libcurl Version: libcurl/7.38.0 OpenSSL/1.0.1h zlib/1.2.8
J2C Decoder Version: KDU v7.0
Audio Driver Version: FMOD Ex 4.44.31
Qt Webkit Version: 4.7.1 (version number hard-coded)
Voice Server Version: Vivox 4.6.0009.20030

Built with MSVC version 1600
Packets Lost: 19/10,879 (0.2%)

TankMaster Finesmith commented at 2014-11-19T06:53:59Z

on build 296857, I get:
GeForce Titan - High-Ultra
AMD R9 290X - High-Ultra
Intel HD5000 - Mid-High
Intel HD4600 - Mid
Intel HD4400 - Low-Mid

Whirly Fizzle commented at 2014-11-25T01:12:27Z

@kyle @graham

Is it expected that cards that were previously blocked (unsupported) in the GPU table are able to login on the Benchmark viewer?
See BUG-7896 for one example

Kyle Linden commented at 2014-12-02T23:12:42Z

Hello Whirly,

Previously blocked (unsupported) cards may very well allow login now with benchmark, but they are still considered unsupported.

Thanks!

Kyle Linden commented at 2014-12-02T23:15:01Z

Thank you everyone for your patience. We have a new viewer release candidate that addresses this crash on launch issue. Please give it a try.

http://wiki.secondlife.com/wiki/Release_Notes/Second_Life_Release/3.7.22.297128

Thanks!