* Run the tests with firebug/chrome developer tools active (will
  describe how to activate and use these below)
* Add info to the JIRA describing:
      o what page did it happen on
      o what test (if any)
      o if you are able to reproduce, the steps to do this
      o any information from firebug/chrome that you think might be
        helpful - especially look in the NET tab - we suspect the
        error might be due to an invalid/illegal request for data
      o potentially a screenshot - including your firebug/chrome -
        Please mention the filename of the screenshot in your
        comment - screenshots and comments arent linked in JIRA, so
        it can be quite confusing with several images unless the
        filename is mentioned in the comment.
      o the time and date that this occurred (for reference in logs)

Hi All, As you may have seen on the lists and IRC, there is a reoccurring bug: 'the spinning wheel of death', that we are having a hard time pinning down the causes of. This is the bug where the application hangs on the spinner (the one indicating something is loading) - it just stays there and nothing else happens. As said, we are not quite sure what causes this bug, so it would be very helpful if everyone could keep an extra eye out for it, and give information on when it occurred and optimally some output from firebug or chrome's developer tools. The JIRA for this bug is <http://issues.collectionspace.org/browse/CSPACE-4125>. It would be helpful if you could: * Run the tests with firebug/chrome developer tools active (will describe how to activate and use these below) * Add info to the JIRA describing: o what page did it happen on o what test (if any) o if you are able to reproduce, the steps to do this o any information from firebug/chrome that you think might be helpful - especially look in the NET tab - we suspect the error might be due to an invalid/illegal request for data o potentially a screenshot - including your firebug/chrome - Please mention the filename of the screenshot in your comment - screenshots and comments arent linked in JIRA, so it can be quite confusing with several images unless the filename is mentioned in the comment. o the time and date that this occurred (for reference in logs) Remember that any information is useful - if you find firebug too confusing/technical to use, a description of page/test/actions leading up to the spinner bug would still be helpful - the more scenarios the easier it will be for us narrow down the causes of this bug. Below are information on how to enable firebug and chrome dev tools. *Firebug:* If you are testing with Firefox, you can download the plugin called firebug. This enables you to break on errors, see the network activity, etc. Once downloaded, you enable it by right clicking the little bug in the bottom right corner of firefox and choose "Enable all panels". The places to look for odd behavior when you experience the spinner bug would be the script, net and console tabs - in particular the net tab looking for anything that failed or is stalling *Chrome developer tools:* If you are testing using chrome, you can use the build in developer tools. These are enabled by clicking the Wrench menu -> Tools -> Developer Tools (or clicking ctrl+shift+i). As in firebug, the most interesting tabs here are Network, Console and scripts - in particular network - looking for anything that failed or is stalling. Thanks a lot, ~Kasper