Skip to content
This repository has been archived by the owner on Mar 28, 2024. It is now read-only.

[BUG-226949] Initializing VFS is delayed by 5-10 minutes on Win10 x64 with Intel HD2000 #5383

Open
2 tasks
sl-service-account opened this issue May 6, 2019 · 1 comment

Comments

@sl-service-account
Copy link

sl-service-account commented May 6, 2019

What just happened?

Initializing VFS is delayed by 5-10 minutes on Win10 x64 with Intel HD2000.

What were you doing when it happened?

On the latest Win10 x64 with Intel HD2000 video card install and launch
'http://automated-builds-secondlife-com.s3.amazonaws.com/ct2/36695/308061/Second_Life_6_2_1_526831_i686_Setup.exe' (32-bit)

What were you expecting to happen instead?

The viewer is launched normally on Win10 x64 with Intel HD2000.

Other information

2019-05-06T11:07:35Z INFO #RenderInit# newview/llfeaturemanager.cpp(310) LLFeatureManager::parseFeatureTable : Found feature table version 33
2019-05-06T11:12:17Z INFO # newview/llglsandbox.cpp(1120) gpu_benchmark : Memory bandwidth is 0.062GB/sec according to CPU timers

This issue was found during ad-hoc testing.
This issue is reproduced on the current release 6.2.0.526190 viewer.
This issue is reproduced when trying to launch a 32-bit viewer.
Actual OS Version: Microsoft Windows 10 Pro (10.0.17763).
The viewer identifies OS Version: Microsoft Windows 8 64-bit (Build 9200)

Attachments

Links

Duplicates

Original Jira Fields
Field Value
Issue BUG-226949
Summary Initializing VFS is delayed by 5-10 minutes on Win10 x64 with Intel HD2000
Type Bug
Priority Unset
Status Accepted
Resolution Accepted
Labels vfs_delay
Reporter KonstantinM ProductEngine (konstantinm.productengine)
Created at 2019-05-06T11:24:55Z
Updated at 2019-08-26T15:03:39Z
{
  'Build Id': 'unset',
  'Business Unit': ['Platform'],
  'Date of First Response': '2019-05-06T07:21:23.074-0500',
  "Is there anything you'd like to add?": 'This issue is reproduced on the current release 6.2.0.526190 viewer.\r\nThis issue is reproduced when trying to launch a 32-bit viewer.\r\nActual OS Version: Microsoft Windows 10 Pro (10.0.17763).\r\nThe viewer identifies OS Version: Microsoft Windows 8 64-bit (Build 9200)',
  'ReOpened Count': 0.0,
  'Severity': 'Unset',
  'System': 'SL Viewer',
  'Target Viewer Version': 'viewer-development',
  'What just happened?': 'Initializing VFS is delayed by 5-10 minutes on Win10 x64 with Intel HD2000.',
  'What were you doing when it happened?': "On the latest Win10 x64 with Intel HD2000 video card install and launch\r\n'http://automated-builds-secondlife-com.s3.amazonaws.com/ct2/36695/308061/Second_Life_6_2_1_526831_i686_Setup.exe' (32-bit)",
  'What were you expecting to happen instead?': 'The viewer is launched normally on Win10 x64 with Intel HD2000.',
}
@sl-service-account
Copy link
Author

Whirly Fizzle commented at 2019-05-06T12:21:23Z, updated at 2019-05-06T12:22:47Z

The log shows the hang is when running the benchmarking - it took nearly 5 minutes to run the benchmark.

2019-05-06T11:07:35Z INFO #RenderInit# newview/llfeaturemanager.cpp(310) LLFeatureManager::parseFeatureTable : Found feature table version 33
2019-05-06T11:12:17Z INFO # newview/llglsandbox.cpp(1120) gpu_benchmark : Memory bandwidth is 0.062GB/sec according to CPU timers
2019-05-06T11:12:17Z INFO # newview/llglsandbox.cpp(1138) gpu_benchmark : Memory bandwidth is 18.609GB/sec according to ARB_timer_query
2019-05-06T11:12:17Z INFO #RenderInit# newview/llfeaturemanager.cpp(679) LLFeatureManager::applyBaseMasks : Setting GPU Class to Class3

The viewer identifies OS Version: Microsoft Windows 8 64-bit (Build 9200)
This is because the 32bit viewer versions are built without the Win 10 manifest as far as I'm aware.

This hang on benchmarking affects at least the Intel HD 2000, 2500 & 3000 cards.
We had the same problem on Firestorm with the benchmarking hang on those cards so the FS solution was to disable benhmarking when using --noprobe & get affected users to use --noprobe.
See: https://hg.phoenixviewer.com/phoenix-firestorm-lgpl/rev/8551133b1d7b - Skip gpu_benchmark if the startup paramert -noprobe is present. This can be used as a last resort option if gpu_bench hangs or crashes (eg on some Intel chipset/driver/windows combination).
Fix is from Nicky Dasmijn who has a CA.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

1 participant