Open sl-service-account opened 5 years ago
Whirly Fizzle commented at 2019-04-25T22:36:46Z
Hiya jmanque,
I know you said that you couldn't reproduce the problem using another computer on the same network, which indicates this isn't an inventory issue, but there's some odd inventory stuff in your attached log that makes me a bit suspicious that account may have an inventory issue. Can you test uploads on the affected computer using an alt account & report back if you have the same problem?
In your logs, there are many of these lines... 2019-04-24T05:55:11Z WARNING #Inventory# newview/llinventoryobserver.cpp(289) LLInventoryFetchItemsObserver::startFetch : Skip fetching for a NULL uuid Possibly just lots of unedited notecards, I don't know.
The upload errors are odd. You are not just getting those "out of memory" errors when uploading either. For example, you don't seem to be able to get the materials cap because of "out of memory".
2019-04-24T06:04:26Z WARNING #Materials# newview/llmaterialmgr.cpp(106) LLMaterialHttpHandler::onFailure : \n--------------------------------------------------------------------------\nPOST Error[27] cannot access cap 'RenderMaterials'\n with url 'https://sim10536.agni.lindenlab.com:12043/cap/629ed76d-47f8-e562-e8d0-42f42fb91466' because Out of memory\n--------------------------------------------------------------------------
Also "out of memory" again here:
2019-04-24T06:04:35Z WARNING #Avatar# newview/llvoavatarself.cpp(2237) LLVOAvatarSelf::appearanceChangeMetricsCoro : Unable to upload statistics
2019-04-24T06:04:35Z WARNING #CoreHttp# llcorehttp/_httppolicy.cpp(434) LLCore::HttpPolicy::stageAfterCompletion : HTTP request 00000228D03B4AB0 failed after 0 retries. Reason: Out of memory (Easy_27)
2019-04-24T06:04:35Z WARNING #Texture# newview/lltexturefetch.cpp(3996) `anonymous-namespace'::AssetReportHandler::onCompleted : Error delivering asset metrics to grid. Status: Easy_27, Reason: Out of memory
Kyle Linden commented at 2019-04-29T20:26:54Z
Hi jmanque,
The errors in your Second Life logs are interesting, I don't think I've seen those before.
I know you said that you reproduced this issue on HIppotropolis as well as in the regions based on the log files. My concern is that the regions reflected in the logs were extremely busy at the time of the errors, based on the log timestamps.
Will you please attempt to reproduce this issue in a different, quiet empty region and provide viewer logs from that session too.
Please also update the environment with exact viewer information from Help > About Second Life. It doesn't immediately matter that you switch between Second Life and Firestorm, but I cannot effectively troubleshoot this issue unless you are using the Second Life viewer and I know exactly which one.
Please let me know and press the Info Provided button when you update this report.
Thanks!
jmanque commented at 2019-04-30T05:37:50Z
I tried uploading again. This time in Hippotropolis. One time I was definitely alone on the sim. The other there may have been one other avatar. I used my standard account and an alt as requested. Both times failed. I've attached the log files. I also tried uploading using the other computer, same account, same network, and it succeeded again.
Below find the Environment-
System Information-
Second Life Release 6.2.0.526190 (64bit)
Release Notes
You are at 128.0, 128.0, 30.3 in Hippotropolis located at sim10531.agni.lindenlab.com (216.82.52.37:13009)
SLURL: http://maps.secondlife.com/secondlife/Hippotropolis/128/128/30
(global coordinates 238,464.0, 244,864.0, 30.3)
Second Life RC BlueSteel 19.04.22.526534
Release Notes
CPU: AMD A10-6700 APU with Radeon(tm) HD Graphics (3693.09 MHz)
Memory: 11446 MB
OS Version: Microsoft Windows 10 64-bit (Build 17763)
Graphics Card Vendor: ATI Technologies Inc.
Graphics Card: AMD Radeon HD 8670D
Windows Graphics Driver Version: 15.201.1151.1008
OpenGL Version: 4.2.13399 Compatibility Profile Context 15.201.1151.1008
Window size: 1335x808
Font Size Adjustment: 96pt
UI Scaling: 1
Draw distance: 128m
Bandwidth: 3000kbit/s
LOD factor: 1.125
Render quality: 3
Advanced Lighting Model: Enabled
Texture memory: 512MB
VFS (cache) creation time: April 18 2019 00:27:57
J2C Decoder Version: KDU v7.10.4
Audio Driver Version: FMOD Ex 4.44.64
Dullahan: 1.1.1320 / CEF: 3.3626.1895.g7001d56 / Chromium: 72.0.3626.121
LibVLC Version: 2.2.8
Voice Server Version: Vivox 4.9.0002.30313
Packets Lost: 9/6,515 (0.1%)
April 29 2019 22:07:04
jmanque commented at 2019-04-30T05:39:17Z
System Information-
Second Life Release 6.2.0.526190 (64bit)
Release Notes
You are at 128.0, 128.0, 30.3 in Hippotropolis located at sim10531.agni.lindenlab.com (216.82.52.37:13009)
SLURL: http://maps.secondlife.com/secondlife/Hippotropolis/128/128/30
(global coordinates 238,464.0, 244,864.0, 30.3)
Second Life RC BlueSteel 19.04.22.526534
Release Notes
CPU: AMD A10-6700 APU with Radeon(tm) HD Graphics (3693.09 MHz)
Memory: 11446 MB
OS Version: Microsoft Windows 10 64-bit (Build 17763)
Graphics Card Vendor: ATI Technologies Inc.
Graphics Card: AMD Radeon HD 8670D
Windows Graphics Driver Version: 15.201.1151.1008
OpenGL Version: 4.2.13399 Compatibility Profile Context 15.201.1151.1008
Window size: 1335x808
Font Size Adjustment: 96pt
UI Scaling: 1
Draw distance: 128m
Bandwidth: 3000kbit/s
LOD factor: 1.125
Render quality: 3
Advanced Lighting Model: Enabled
Texture memory: 512MB
VFS (cache) creation time: April 18 2019 00:27:57
J2C Decoder Version: KDU v7.10.4
Audio Driver Version: FMOD Ex 4.44.64
Dullahan: 1.1.1320 / CEF: 3.3626.1895.g7001d56 / Chromium: 72.0.3626.121
LibVLC Version: 2.2.8
Voice Server Version: Vivox 4.9.0002.30313
Packets Lost: 9/6,515 (0.1%)
April 29 2019 22:07:04
Kyle Linden commented at 2019-04-30T19:15:17Z
Hi Jmanque,
Given all of that new information and logs, I checked with one of our devs and we are suspicious that your system may have bad RAM chips.
Please review the following articles to help you assess whether or not your RAM is faulty. https://www.windowscentral.com/how-check-your-pc-memory-problems-windows-10 https://www.pcworld.com/article/3040544/do-you-have-bad-ram-heres-how-to-find-out.html
If your RAM checks out as OK then it may be that some other application is limiting Second Life from accessing the memory of your system. That will require further investigation.
Please let me know if your memory has faults first and we'll go from there. Press the Info Provided button when you update this report.
Thanks!
jmanque commented at 2019-05-01T00:15:49Z
I ran the Windows Memory Diagnostic Tool as requested. The results were-
The Windows Memory Diagnostic tested the computer's memory and detected no errors
Kyle Linden commented at 2019-05-01T15:22:02Z
Hi Jmanque,
We'll need some additional information then. First please run your Anti-virus and any anti-malware programs you have to confirm your system is free of malicious software.
Then please go to your Windows menu and select Run and type in: dxdiag Once that program has opened and gathered all your hardware information use its Copy to file option. Save that information and then attach it to this Jira.
Next, please install the free version of CCleaner from https://www.ccleaner.com/download Open CCleaner, go to Tools > Uninstall, then in the bottom right choose Save to Textfile. It looks like this: https://prnt.sc/lfj7e4 Attach the resulting file to this Jira. This will give a list of all software installed on your system so we can look for a possible culprit that's interfering with Second Life accessing memory.
Please press the info Provided Button when you update this report.
Thanks!
jmanque commented at 2019-05-02T23:20:07Z, updated at 2019-05-02T23:25:20Z
I ran Malwarebytes and Windows defender. The results were-
Malwarebytes- Your scan is complete. No threats detected!
Windows Defender- 0 threats found.
-I'm attaching the file of installed programs as requested, as well as DxDiag.txt.
Kyle Linden commented at 2019-05-03T17:11:19Z
Hi jmanque,
Thank you for the updated information.
Let's try this. Please create a new Windows User profile on your computer and make it an Admin. With the new Windows User, download and install a fresh copy of Second Life from https://get.secondlife.com
If you are still having the issue with a clean Windows User please note the date, time and region in which you reproduced the issue. Please provide the latest copy of the Second Life logs from the new Windows User, and we'll compare those to the server logs.
Please press Info Provided when you update this report.
Thanks!
jmanque commented at 2019-05-07T07:11:23Z
So, I uninstalled the Second Life Viewer, created a new admin account as requested, downloaded the Viewer and installed it in that account, and went to Hippotropolis at 11:42 PM SLT on May 6 and tried a bulk upload- SecondLifeNewAdmin.zip. It worked flawlessly. I then switched back to the old account and logged in at roughly 11:56 PM SLT and tried again, expecting it to fail, but it again uploaded flawlessly- SecondLifeOldAdmin.zip. I'll attach the log files. So, is it some kind of corruption in the original account? Will it reappear if the Viewer upgrades itself and I'm logged into that account?
Kyle Linden commented at 2019-05-07T18:57:56Z
Hi Jmanque,
That is fascinating. While I expected the new Windows Admin account to resolve the issue, I am very surprised that the original account was also resolved. I can't really explain that.
I am happy that the issue was resolved though. In case it returns, I am leaving this issue as Needs More Information. Please update this report if it ever happens again.
Thanks!
What just happened?
After numerous attempts with help groups, none of which have been able to solve this problem, it was suggested that this should be posted as a bug report. The theory most often given is that there is a problem with the way the viewer is interacting with my specific hardware that is causing the problem.
I have been having trouble uploading textures for some time, at least a year. I’m lucky if I can upload once in twenty attempts. If I attempt to upload a single image the preview works, then when I click the final upload button I get an error. If I attempt a bulk upload I get a separate error message for each failed upload. Single of bulk each error reads-
Unable to upload
Original Jira Fields
| Field | Value | | ------------- | ------------- | | Issue | BUG-226857 | | Summary | Unable to upload | | Type | Bug | | Priority | Unset | | Status | Needs More Info | | Resolution | Unresolved | | Reporter | jmanque (jmanque) | | Created at | 2019-04-25T09:04:48Z | | Updated at | 2019-05-07T18:57:55Z | ``` { 'Build Id': 'unset', 'Business Unit': ['Platform'], 'Date of First Response': '2019-04-25T17:36:45.580-0500', "Is there anything you'd like to add?": "Basic fixes I’ve tried within the Viewer-\r\n\r\n*loaded a basic ‘classic’ default avatar\r\n*reduced my inventory. It’s now around 20k items\r\n*tried uploading from ‘quiet’ sims like Hippotropolis\r\n*reduced the size of the viewer window\r\n*tried uploading a 32x32 pixel, 165 byte image\r\n*cleared the cache\r\n\r\nIn Viewer Preferences-\r\n\r\n*Decreased draw distance in increments to 32 meters\r\n*Disabled OpenGL Vertex Buffer Objects\r\n*Set Quality and Speed performance to the lowest ‘speed’ setting in increments\r\n\r\nFixes I’ve tried with the computer-\r\n\r\n*Tried uploading after a fresh reboot with no other software running\r\n*Temporarily disabling automatic backup software\r\n*Temporarily disabling anti-malware software\r\n*Moving textures to upload to the desktop\r\n*Reinstalled the viewer\r\n*Updated Windows 10\r\n*Reinstalled Windows 10 \r\n*Updated the graphics card drivers\r\n*Updated the computer BIOS\r\n\r\nNone of these have had the slightest effect on the problem. I used to upload routinely without a hitch with this same computer, both individual and bulk uploads. The computer is otherwise healthy, has no issues outside SL, and has no other viewer issues inside it, except those caused by the attempted uploads. \r\n\r\nWhile this question is specifically about the Linden Labs viewer, Firestorm also has this problem. The problem started with the Linden Viewer and Firestorm at about the same time. This link may provide insight. According to this page- \r\n\r\nhttps://community.secondlife.com/forums/topic/388344-secondlife-error-in-upload-request/\r\n\r\n-others have been having this issue with every version of FS after 4.7.7, which they say is when the Linden Lab code on which it is based was changed to include CoRoutines. \r\n\r\nBelow is the error message from the log when using the Linden Labs Viewer. I’ll attach the whole log, but this appears to be the cogent section. It specifies an ‘out of memory’ issue, but as previously stated, this same computer uploaded for years without a single problem using default viewer settings, and now, no matter how conservative I get with the settings it doesn’t correct things. When it fails it won’t even upload a 32x32 pixel 165 byte image. The only difference between when things worked and when they failed is the Viewer version, so I don’t know if it’s assigning or accessing memory differently than previous versions, or if this is a bug-\r\n\r\n\r\n2019-04-24T06:04:35Z INFO #HttpCoroutineAdapter#genericPostCoro# llmessage/llcorehttputil.cpp(1313) LLCoreHttpUtil::HttpCoroutineAdapter::trivialPostCoro : Generic POST for https://sim10536.agni.lindenlab.com:12043/cap/9d73d5e3-25f2-61f4-23c3-667b5251c93e\r\n2019-04-24T06:04:35Z INFO # llmessage/llcorehttputil.cpp(282) LLCoreHttpUtil::HttpCoroHandler::onCompleted : Possible failure [Easy_27] cannot POST url 'https://sim10536.agni.lindenlab.com:12043/cap/c4f1b76f-0f53-db3c-357b-f29915a8db10' because Out of memory\r\n2019-04-24T06:04:35Z WARNING #Avatar# newview/llvoavatarself.cpp(2237) LLVOAvatarSelf::appearanceChangeMetricsCoro : Unable to upload statistics\r\n2019-04-24T06:04:35Z WARNING #CoreHttp# llcorehttp/_httppolicy.cpp(434) LLCore::HttpPolicy::stageAfterCompletion : HTTP request 00000228D03B4AB0 failed after 0 retries. Reason: Out of memory (Easy_27)\r\n2019-04-24T06:04:35Z WARNING #Texture# newview/lltexturefetch.cpp(3996) `anonymous-namespace'::AssetReportHandler::onCompleted : Error delivering asset metrics to grid. Status: Easy_27, Reason: Out of memory\r\n2019-04-24T06:04:35Z INFO # newview/llteleporthistory.cpp(227) LLTeleportHistory::dump : Teleport history dump (3 items):\r\n2019-04-24T06:04:35Z INFO # newview/llteleporthistory.cpp(236) LLTeleportHistory::dump : 0: Book Island Publishing Village for books, authors and writers, Book Island REGION_ID: f6f51a64-fdf3-4301-a6f3-f554f1cf5656, pos: { 179277, 268839, 23.9328 }\r\n2019-04-24T06:04:35Z INFO # newview/llteleporthistory.cpp(236) LLTeleportHistory::dump : 1: FaMESHed X :: http://www.fameshedx.com/, Isolated Heights REGION_ID: 7c4adaad-e45f-4021-8206-2ef30f0c30f2, pos: { 252277, 332182, 1000.08 }\r\n2019-04-24T06:04:35Z INFO # newview/llteleporthistory.cpp(236) LLTeleportHistory::dump : * 2: Midas Sponsored by Fallen Gods, Inc., FF Midas REGION_ID: b747b38c-9613-4ef6-952d-527939e1991d, pos: { 129109, 183862, 94.985 }\r\n2019-04-24T06:04:35Z WARNING #CoreHttp# llcorehttp/_httppolicy.cpp(434) LLCore::HttpPolicy::stageAfterCompletion : HTTP request 00000228D03B6410 failed after 0 retries. Reason: Out of memory (Easy_27)\r\n2019-04-24T06:04:35Z INFO # llmessage/llcorehttputil.cpp(282) LLCoreHttpUtil::HttpCoroHandler::onCompleted : Possible failure [Easy_27] cannot POST url 'https://sim10536.agni.lindenlab.com:12043/cap/9d73d5e3-25f2-61f4-23c3-667b5251c93e' because Out of memory\r\n2019-04-24T06:04:35Z INFO #CoreHTTP# llmessage/llcorehttputil.cpp(87) LLCoreHttpUtil::logMessageFail : HttpCoroutineAdapter Possible failure 'Failed to post statistics to sim' for https://sim10536.agni.lindenlab.com:12043/cap/9d73d5e3-25f2-61f4-23c3-667b5251c93e\r\n2019-04-24T06:04:35Z INFO #MarkerFile# newview/llappviewer.cpp(5101) LLAppViewer::sendLogoutRequest : Created logout marker file 'C:\\\\Users\\\\BAM\\\\AppData\\\\Roaming\\\\SecondLife\\\\logs\\\\SecondLife.logout_marker' \r\n2019-04-24T06:04:35Z INFO # newview/llviewerwindow.cpp(4492) LLViewerWindow::saveSnapshot : Saving snapshot to: C:\\\\Users\\\\BAM\\\\AppData\\\\Roaming\\\\SecondLife\\\\jmanque_resident\\\\screen_last.bmp\r\n2019-04-24T06:04:35Z INFO #Settings# llxml/llcontrol.cpp(844) LLControlGroup::saveToFile : Saved to C:\\\\Users\\\\BAM\\\\AppData\\\\Roaming\\\\SecondLife\\\\user_settings\\\\settings.xml\r\n2019-04-24T06:04:35Z INFO #Settings# llxml/llcontrol.cpp(844) LLControlGroup::saveToFile : Saved to C:\\\\Users\\\\BAM\\\\AppData\\\\Roaming\\\\SecondLife\\\\user_settings\\\\settings.xml\r\n\r\n__________ \r\n\r\nIf this is an actual bug it would be nice to have it squashed. If it’s just a user error it would be nice to know what it is. ", 'ReOpened Count': 0.0, 'Severity': 'Unset', 'System': 'SL Viewer', 'Target Viewer Version': 'viewer-development', 'What just happened?': 'After numerous attempts with help groups, none of which have been able to solve this problem, it was suggested that this should be posted as a bug report. The theory most often given is that there is a problem with the way the viewer is interacting with my specific hardware that is causing the problem. \r\n\r\nI have been having trouble uploading textures for some time, at least a year. I’m lucky if I can upload once in twenty attempts. If I attempt to upload a single image the preview works, then when I click the final upload button I get an error. If I attempt a bulk upload I get a separate error message for each failed upload. Single of bulk each error reads-\r\n\r\nUnable to upload\r\n