Steps to Reproduce

• Login to any region - main channel or an RC region.

• Go to Help -> About Second Life

• Observe if the server release notes fetch.

• Close Help -> About Window & reopen it.

  Observed Behaviour

• When you first open Help -> About Second Life in the session, the server release notes URL stays stuck on "Retrieving..."

• See Fig 1.

• After closing & reopening the Help -> About floater, you will always see "Error fetching server release notes URL."

• See Fig 2.

• The server release notes URL has not been loading for a good while now on any region.

• I think this problem may only affect viewers using Coroutines.

• Bug does not reproduce on the Obsolete Platforms viewer Second Life 3.7.28 (300847) Apr 13 2015 15:22:33 (Obsolete) or on Firestorm 4.7.7 release (which does not have coroutines merged in).
  Bug does however reproduce on Firestorm on builds after the coroutines merge.

• Fig 3 shows the server release notes URL loading as expected on the Obsolete Platforms viewer.

• Logs show:

  2016-08-03T04:22:30Z INFO: LLSDXMLParser::Impl::parse: LLSDXMLParser::Impl::parse: XML_STATUS_ERROR parsing:		<div id="contentSub"><span class="subpages">&lt; <a href="/wiki/Release_Notes" title="Release Notes">Release Notes</a>&lrm; | <a href="/wiki/Release_Notes/Second_Life_RC_BlueSteel" title="Release Notes/Second Life RC BlueSteel">Second Life RC BlueSteel</a></span></div>

  Expected Behaviour

  Server release notes URL should fetch.

Attachments

• Fig 1 - first opening of About Second Life.png 2016-08-03 00:38:34
• Fig 2 - Second opening of About Second Life.png 2016-08-03 00:38:34
• Fig 3 - Expected behaviour on Obsolete Platforms viewer.png 2016-08-03 00:38:34

{
  'Business Unit': ['Platform'],
  'Date of First Response': '2016-08-06T08:23:19.727-0500',
  'ReOpened Count': 0.0,
  'Regression?': ['Issue is a Regression'],
  'Severity': 'Unset',
  'System': 'SL Viewer',
  'Target Viewer Version': 'viewer-development',
  'What just happened?': 'Filling in...',
  'What were you doing when it happened?': '...',
  'What were you expecting to happen instead?': '...',
}