Hi,
I am running version 2.0.0.227 I have been playing with the monitoring state of shows and episodes, just stress testing it, changing their status lots over and over, eventually the interface becomes unresponsive. no errors that I can see but the monitored status change takes lounger and longer to update and then eventually the series pages wont even display.
The weird thing is if I close and reopen the browser it all starts working again.
Browsers I was testing with IE 10 and FireFox 23.0.1
Made a couple changes in the develop branch that should help with this. Roughly how many clicks does it take before it starts to fail? Does memory usage of the browser increase until it stop responding?
About 10 to 20 clicks would make is slower, another 10 to 20 and the shows would stop displaying (the epp list would not display).
Mem usage in IE peeks at about 60 Meg.
I also received the following errors when testing today:
“MissingLayout.js : 65
Unable to get property ‘show’ of undefined or null reference”
“SeriesDetailsLayout.js : 178
Unable to get property ‘show’ of undefined or null reference”
It is not the monitoring status updating that is causing the problem.
It is just switching shows, I have about 6 shows in my list, if I rapidly switch between them by clicking on the series link at the top and then selecting a show then click on the series link at the top and select the next show, after about 10 or so it stops responding and show episodes stop displaying, and monitoring status changes takes ages.
I have switch to dev (2.0.0.255) and the problem is still there.
to me it sounds like a memory leak. I’ll take a look to see if I can track it down.
Private Bytes of Firefox in a 5 min test, in this time it became unresponsive multiple times and was reset by simply pasting the root URL into the location bar, not restarting the browser or tab, all tests were done in the same tab for this 5 min test.
The image shows mem usage 30 = 300Meg
Some more info, it is weird, if I leave the same tab open and select show after show until the problem occurs then just past the root url (http://192.168.0.15:8989) into he location bar I see the loading screen again with the ver and the animated circles going back are forth for a few seconds and then the interface shows up, when this happens it looks like it resets the instance of this session and the shows work again for anther 10 or so goes. So the browser does not have to be restarted just the instance of the session by re-entering the url from scratch.
App being fixed by reloading the page is completely normal. NzbDrone is a single page app. thats why its very responsive, the page never get reloaded unless the user does it manually.
when you reload the page everything starts from scratch, thats why it fixes it.
So are you able to reproduce this?
Do you need a log or is there a particular browser you want tested?
I was able to reproduce it. there is a card on trello if you want to keep track.
just confirming, unhooking signalr worked, I can click through show now without an issue.
is the problem with signalr in the lib or in how it is being used?
good to hear, it was how we used it. we should be able to fix it.