We seem to fairly often have an issue where when a specific release is clicked, the page never loads, the spinner just sits there forever.
It seems to crop up most often when we create a new release, though that might not actually be the case. This will happen for any previous release also. Other pages (i.e. the list of releases) load OK.
The following three ajax requests continue to return a 200 code in the background every few seconds ( have attached a full network dump of these requests)
http://[Removed]/api/releases/releases-802/deployments
http://[Removed]/api/artifacts?regarding=releases-802
http://[Removed]/api/events?regarding=releases-802
http://[Removed]/api/releases/releases-802/progression
I have upgraded to Octopus 2.6.2.845 and also done a database repair and the problem persists. This is on both IE11 and Chrome 40.0.2214.111 m. The home, log and database folders are on a network share, though this does not generally seem to be a problem. Our database file is about 25MB with the database folders totalling about 96MB, so not that big.
We don’t seem to have a workaround for this, just that eventually it will work again. Sometimes restarting the Octopus service seems to help, sometimes not. Our octopus server process seems to run around the 350-400MB memory usage mark, which seems quite high?
NetworkData.xml (52 KB)