Crashing on Synology DS1812+ (exception while processing action request)

[catmur]

Hi,
I'me a newbie to MinimServer. I've just installed Java (1.7.0_67) onto my Synology 1812+, and the package "MinimServer-0.8.2-x86.spk".
the install went fine on the Synology, and so did the client (on a Windows 8.1 machine).
When browsing the media server using Windows Media player, I'm getting occasional (i can't pin it to a specific action) crashes, with the following in the logs:

MinimServer[DISKSTATION] is running
MinimServer: exception while processing action request: java.lang.StringIndexOutOfBoundsException: String index out of range: 0
java.lang.StringIndexOutOfBoundsException: String index out of range: 0
at java.lang.String.charAt(String.java:658)
at com.minimserver.Server$TagContainer.childObject(Server.java:12849)
at com.minimserver.Server.getContained(Server.java:5385)
at com.minimserver.Server.findContained(Server.java:5409)
at com.minimserver.Server.access$16500(Server.java:91)
at com.minimserver.Server$ContentDirectoryProvider.doBrowse(Server.java:15354)
at com.minimserver.Server$ContentDirectoryProvider.browse(Server.java:15302)
at org.openhome.net.device.providers.DvProviderUpnpOrgContentDirectory1$DoBrowse.ac​tionInvoked(DvProviderUpnpOrgContentDirectory1.java:978)
MinimServer error: now stopped, use 'relaunch' or 'exit'
starting MinimServer[DISKSTATION]

I've no idea where to start debugging this... any thoughts?

[catmur]

to add... I seem to be able to force the error to occur...

In windows media player, if I browse the media server then select (from the left navigation tree) either Artist, Album or Genre, and then right click and entry in in the main window, i get a notification that the server has thrown an exception

[simoncn]

(19-08-2014 11:31)catmur Wrote:  to add... I seem to be able to force the error to occur...

In windows media player, if I browse the media server then select (from the left navigation tree) either Artist, Album or Genre, and then right click and entry in in the main window, i get a notification that the server has thrown an exception

I tried this and I'm not seeing the problem.

This crash could occur if WMP is sending MinimServer a request in an unexpected (incorrect) format.

Please do the following:

1) From the minim icon, select 'Show log'
2) In the log window, change the logging level to Debug
3) Leave the log window open
4) From the minim icon, select 'Restart'
5) In WMP, force the crash with as few steps as possible
6) In the log window, click 'Save as' to save a log file
7) In the log window, change the logging level back to Info
8) Zip the log file and attach it to a post here

Many thanks!

[catmur]

(19-08-2014 13:13)simoncn Wrote:  I tried this and I'm not seeing the problem.

This crash could occur if WMP is sending MinimServer a request in an unexpected (incorrect) format.

Please do the following:

1) From the minim icon, select 'Show log'
2) In the log window, change the logging level to Debug
3) Leave the log window open
4) From the minim icon, select 'Restart'
5) In WMP, force the crash with as few steps as possible
6) In the log window, click 'Save as' to save a log file
7) In the log window, change the logging level back to Info
8) Zip the log file and attach it to a post here

Many thanks!

Hi Simon, thanks for the quick response. Attached is the debug log file, and a video showing the event.

[simoncn]

(19-08-2014 17:22)catmur Wrote:  Hi Simon, thanks for the quick response. Attached is the debug log file, and a video showing the event.

There are no attachments to your post. To add an attachment, you need to select the file using the New Attachment button and then click the Add Attachment button.

[catmur]

Quote:There are no attachments to your post. To add an attachment, you need to select the file using the New Attachment button and then click the Add Attachment button.

Doh, one of the files was over the limit, but I hadn't noticed. Attahced to this one is the log file.

[catmur]

Quote:Doh, one of the files was over the limit, but I hadn't noticed. Attached to this one is the log file.

And this attachement has the screen capture (mp4) of the event happening.

[simoncn]

(19-08-2014 18:16)catmur Wrote:  Doh, one of the files was over the limit, but I hadn't noticed. Attahced to this one is the log file.

Thanks for these files. I've looked at the video and it seems the same as what I have been trying. The log file shows the incorrect request (with the invalid container ID 0$), but it doesn't include the previous browsing/searching history. This is important because there might be a bug in MinimServer that has caused it to send this invalid container ID to WMP in a previous response.

To capture a trace log of the previous browsing/searching history, please do the following:

1) Close WMP
2) From the Synology admin UI, restart MinimServer
3) From the minim icon, select 'Show log'
4) In the log window, change the logging level to Trace
5) Start WMP
6) In WMP, force the crash with as few steps as possible
7) In the log window, change the logging level back to Info
8) Use File Station on the Synology to find the MinimServer/appData folder and upload the minimserver.log file from that folder to your PC
9) Zip the log file and attach it to a post here

Thanks very much!

[catmur]

(19-08-2014 18:41)simoncn Wrote:  Thanks for these files. I've looked at the video and it seems the same as what I have been trying. The log file shows the incorrect request (with the invalid container ID 0$), but it doesn't include the previous browsing/searching history. This is important because there might be a bug in MinimServer that has caused it to send this invalid container ID to WMP in a previous response.

To capture a trace log of the previous browsing/searching history, please do the following:

1) Close WMP
2) From the Synology admin UI, restart MinimServer
3) From the minim icon, select 'Show log'
4) In the log window, change the logging level to Trace
5) Start WMP
6) In WMP, force the crash with as few steps as possible
7) In the log window, change the logging level back to Info
8) Use File Station on the Synology to find the MinimServer/appData folder and upload the minimserver.log file from that folder to your PC
9) Zip the log file and attach it to a post here

Thanks very much!

Attached

[simoncn]

(19-08-2014 18:53)catmur Wrote:  

(19-08-2014 18:41)simoncn Wrote:  1) Close WMP
2) From the Synology admin UI, restart MinimServer
3) From the minim icon, select 'Show log'
4) In the log window, change the logging level to Trace
5) Start WMP
6) In WMP, force the crash with as few steps as possible
7) In the log window, change the logging level back to Info
8) Use File Station on the Synology to find the MinimServer/appData folder and upload the minimserver.log file from that folder to your PC
9) Zip the log file and attach it to a post here

Thanks very much!

Attached

Thanks for this. Unfortunately, it seems that the logging level was set to Debug, not Trace (see step 4 above). Could you rerun this with the logging level set to Info when MinimServer starts and change the logging level to Trace at step 4 before WMP starts?