Page 1 of 1

2 Bugs: Dsub crashes server, cache alphabetical order.

PostPosted: Wed Jun 26, 2013 1:26 am
by moonman
I'm running the Subsonic for unRAID plugin on my home server (jangjong's). I recently moved from iOS to Android and up until now it never skipped a beat. Streaming, caching all worked fine. I installed Dsub for android and was perplexed to find that when I try to stream or cache it randomly crashes the server. I can usually get around 5 albums cached before it starts going awry. Then when I try to browse the library or play a song through the app it times out, and when I open the web interface with a browser to see what's going on it doesn't load. I then try to stop and reboot the unRAID server from within the unRAID menu and the unRAID menu freezes also and I have to reboot the unRAID server manually and start Subsonic again. None of this has happened when I stream via my old iPhone or through the web interface.

My second bug relates to the way the offline caching works. When I browse the library in online mode artists show up alphabetically, but when I do it in offline mode some artists beginning with L show up at the start before A, some show up in their correct order, and others show up at the end after Z. It appears to only happen with artists beginning with L, though I haven't yet managed to cache enough artists onto the phone to actually tell for sure.

This seems like a great app, but these problems cripple it. Would be good to know whether there is a fix.


EDIT: I should also add what hardware/versions I'm using. The Subsonic version is jangjong's latest unRAID plugin version 4.8 (build 3434), Dsub is the latest version from the Play store and the phone is Samsung Galaxy S4 Qualcomm version GT-I9505.

Re: 2 Bugs: Dsub crashes server, cache alphabetical order.

PostPosted: Wed Jun 26, 2013 3:12 am
by daneren2005
There is nothing the app can do that crashes a server. It sounds like a server problem to me...

As for the second problem, do any of the artists begin with one of these words: "The El La Los Las Le Les"? In both offline mode and online mode it should be pretending they aren't there for purpose of the sort. If it isn't, can you give me an example Artist that shows up in the wrong spot and I can test with it and see if I can reproduce it on my side.

Re: 2 Bugs: Dsub crashes server, cache alphabetical order.

PostPosted: Fri Jun 28, 2013 3:34 pm
by moonman
Hi Daneren, thanks for your prompt response.

I've been playing with the app again over the last couple of days and now downloading appears to be running smoothly. I haven't had another crash and I've added around 1GB of music to the app's cache in that time so the problem appears to have disappeared as promptly and inexplicably as it appeared. If you're certain it's not possible for an app to cause a server crash then it's just an unusual coincidence that it started occurring on the day that I changed to Dsub. I will keep an eye out over on the unRAID forum in case anyone else has been having the same problem.

I am still having the same problem with incorrectly sorting L bands in the offline cache though and none of them begins with any of those words. I have attached three screenshots below. The first shows two L artists showing up at the start of the list, the second shows two artists in their correct places and the third shows an artist which shows up somewhere between V and W.

http://img29.imageshack.us/img29/8391/3t3.png
http://img825.imageshack.us/img825/4672/9i3d.png
http://img19.imageshack.us/img19/932/94vi.png

Re: 2 Bugs: Dsub crashes server, cache alphabetical order.

PostPosted: Fri Jun 28, 2013 3:47 pm
by mr_nobody
moonman wrote:Hi Daneren, thanks for your prompt response.

I've been playing with the app again over the last couple of days and now downloading appears to be running smoothly. I haven't had another crash and I've added around 1GB of music to the app's cache in that time so the problem appears to have disappeared as promptly and inexplicably as it appeared. If you're certain it's not possible for an app to cause a server crash then it's just an unusual coincidence that it started occurring on the day that I changed to Dsub. I will keep an eye out over on the unRAID forum in case anyone else has been having the same problem.

I am still having the same problem with incorrectly sorting L bands in the offline cache though and none of them begins with any of those words. I have attached three screenshots below. The first shows two L artists showing up at the start of the list, the second shows two artists in their correct places and the third shows an artist which shows up somewhere between V and W.

http://img29.imageshack.us/img29/8391/3t3.png
http://img825.imageshack.us/img825/4672/9i3d.png
http://img19.imageshack.us/img19/932/94vi.png


In fact, all of your screwed up examples do start with La/Le which are the equivalent of "the" in french. Of course, it should need a space after those two letters to trigger the ignore but it's pretty clear that's the issue imo.

Re: 2 Bugs: Dsub crashes server, cache alphabetical order.

PostPosted: Fri Jun 28, 2013 5:36 pm
by daneren2005
Good catch mr_nobody. Yes, looking at the code and it looks like I stupidly just did a check if the letters matched those ignore words, not if the first WORD matches them. It will be fixed in the next release. I'm surprised this wasn't noticed sooner to be honest. Sorry for the inconvenience.

As for the server crash, it may be that DSub was using one of the methods that caused the crash, but that is still not the same thing as DSub CAUSING the crash. My point is that there should never ever be anything a client can do to crash the server (and at least with my server there doesn't seem to be). If it happens again before you restart the service you can try copying the subsonic.log over here. It might help find out which particular method is the problem.

Re: 2 Bugs: Dsub crashes server, cache alphabetical order.

PostPosted: Wed Jul 03, 2013 5:32 am
by moonman
daneren2005 wrote:If it happens again before you restart the service you can try copying the subsonic.log over here. It might help find out which particular method is the problem.

Will do, thanks mate.