Viewer Log Decoder Ring
Revision as of 13:25, 30 May 2012 by Dan Linden (talk | contribs) (Created page with "Category:Quality Assurance =Purpose= Document the errors, warnings and infos as we notice them in the viewer log file, and try to understand what they mean. This is not a p…")
Purpose
Document the errors, warnings and infos as we notice them in the viewer log file, and try to understand what they mean. This is not a project to document all messages, just the messages that seem important right now.
Secondary purpose: Reduce the spam where possible. Open jira issues for log messages that seem like spam and ask that they be removed or lower their message level.
template:Log Message
- Date this message was noticed: 2012-mm-dd
- Related Jira issue(s):
- What is the meaning of this message? ie. Is the sky falling or infrequent bug or just recording metrics?
- Is there any workarounds?
- Is this a vital message or spam that can be culled?
Errors
none yet
Warnings
Could not find vertex shader attribute '[something]' to match BindAttributeLocation request.
- Date this message was noticed: 2012-05-29
- Related Jira issue(s): VWR-29016. This was observed on a Mac.
- What is the meaning of this message? Spam
- Is there any workarounds? unknown
- Is this a vital message or spam that can be culled? Runitai says this spam is expected on some systems. It could be removed, but is not a priority right now.
LLHUDManager::sendEffects: Trying to send dead effect!
- Date this message was noticed: 2012-05-29
- Related Jira issue(s): unknown. This warning appeared immediately following a teleport.
- What is the meaning of this message? ie. Is the sky falling or infrequent bug or just recording metrics?
- Is there any workarounds? unknown
- Is this a vital message or spam that can be culled? unknown
LLVOAvatar::getTargetAttachmentPoint: Object attachment point invalid: 127
- Date this message was noticed: 2012-05-29
- Related Jira issue(s): unknown. This message often precedes a 'INFO: LLVOAvatar::processAvatarAppearance: Number of params in AvatarAppearance msg (218) does not match number of tweakable params in avatar xml file' message
- What is the meaning of this message? ie. Is the sky falling or infrequent bug or just recording metrics?
- Is there any workarounds? unknown
- Is this a vital message or spam that can be culled? unknown
LLURLRequest::process_impl: URLRequest Error: 3, URL using bad/illegal format or missing URL, <EMPTY URL>
- Date: 2012-05-22
- Related Jira issue(s): MAINT-1064, MAINT-1066
- What is the meaning of this message? Unknown
- Is there any workarounds? Relog.
- Is this a vital message or spam that can be culled? It seems important.
LLViewerParcelMgr::requestParcelMediaURLFilter: can't get ParcelMediaURLFilterList cap
- Date: 2012-05-22
- Related Jira issue(s): none
- What is the meaning of this message? Unknown. This warning appears 4 times when you edit an object. I suspect it is polling More Info > "Weights of Selected". Does anything else trigger this?
- Is there any workarounds? Unknown
- Is this a vital message or spam that can be culled? Unknown
LLTextureFetchWorker::doWork: Texture missing from server (404)
- Date: 2012-05-22
- Related Jira issue(s): VWR-29020
- What is the meaning of this message? The world map image is missing.
- Is there any workarounds? Unknown, but it's not serious because the map texture appears anyways.
- Is this a vital message or spam that can be culled? Unknown
Infos
LLVOAvatar::processAvatarAppearance: Number of params in AvatarAppearance msg (218) does not match number of tweakable params in avatar xml file (251). Processing what we can. object:
- Date this message was noticed: 2012-05-29
- Related Jira issue(s): unknown. This message is often (always?) followed by a 'WARNING: LLVOAvatar::getTargetAttachmentPoint: Object attachment point invalid: 127' message.
- What is the meaning of this message? ie. Is the sky falling or infrequent bug or just recording metrics?
- Is there any workarounds?
- Is this a vital message or spam that can be culled?
LLSDXMLParser::Impl::parse: LLSDXMLParser::Impl::parse: XML_STATUS_ERROR parsing:cap invocation rate exceeded:
- Date this message was noticed: 2012-05-25
- Related Jira issue(s): none
- What is the meaning of this message? ie. Is the sky falling or infrequent bug or just recording metrics?
- Is there any workarounds?
- Is this a vital message or spam that can be culled?
- Note: My avatar appeared naked/unbaked in this session but I don't know if is related.