Subsonic Fundamentally Broken in Microsoft Edge.

[kosmos]

Greetings Forum,

Ever since the 6.1 release of Subsonic, almost any track played via Subsonic's web interface via Microsoft Edge plays for a few seconds then stops playing. The browser Tab/instance then enters a loop from which the only escape is to kill the browser or wait for it to crash. This behaviour is predictable to an extent, in that once it happens with a track it will always happen with that track irrespective of whether the browser cache is cleared. Interestingly when using Microsoft Edge to connect to Subsonic the username appears as '<whatever>@isub' as opposed to <whatever>@subsonic

In addition to the above, using Subsonic in either Chrome or Firefox results in playlists failing to advance to the next track. This behaviour doesn't happen in every instance, but when it happens, the song that it happened on will continue to fail to advance to the next track irrespective of its arrangement in a playlist and/or Browser Cache clearing.

The playlist progression bug is replicable on Mac OS as well as Microsoft based OS's. These issues have been affecting playback for months, as I mentioned since ver. 6.1 beta and both are present in 6.1.1. My Server is a dedicated Windows Server 2008 R2 system running with 16GB of RAM and a i7 4770K CPU.

[acroyear]

I was just talking about the "failing to advance" problem back in the thread we'd used to discuss it earlier this year.

Can you, on chrome, have the browser javascript/debugging console window open and see if this message comes up?

Code: Select all

Uncaught (in promise) DOMException: The play() request was interrupted by a call to pause(). https://goo.gl/LdLk22

I don't have a fix yet, but this would lead me closer to one for my own product and may help Sindre fix the main UI if that's the case.