Bug 15477 - New track stream can get (superfluous) packets from old stream
: New track stream can get (superfluous) packets from old stream
Status: CLOSED FIXED
Product: Logitech Media Server
Classification: Unclassified
Component: Streaming From SlimServer
: 7.3.0
: PC Debian Linux
: P2 normal (vote)
: 7.5.0
Assigned To: Alan Young
:
Depends on:
Blocks: 11506
  Show dependency treegraph
 
Reported: 2010-01-15 05:17 UTC by Alan Young
Modified: 2010-04-08 17:24 UTC (History)
0 users

See Also:
Category: Bug


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Alan Young 2010-01-15 05:17:38 UTC
There are cases, especially with proxied streaming, where SbS will not have *finished* streaming the track that is playing out and where the player has actually received all the deta necessary to complete the track, and therefore both the source stream connection and the player stream connection remain open. 

This is especially likely with self-terminating (internally delimited) stream content, such as WMA.

Race conditions exist such that player stream connection for the next track can be sent tail-end data packets for the previous track, and where the player stream connection for the previous track can consume packets for the next track.
Comment 1 Alan Young 2010-01-15 05:18:17 UTC
Update hours
Comment 2 SVN Bot 2010-01-15 05:26:39 UTC
 == Auto-comment from SVN commit #29821 to the slim repo by ayoung ==
 == https://svn.slimdevices.com/slim?view=revision&revision=29821 ==

bug 15477: New track stream can get (superfluous) packets from old stream. 
Ensure old source stream is closed before opening new one.
Ensure old player stream is closed before opening new one and discard any pending data for player at that time.
Comment 3 SVN Bot 2010-01-15 05:37:06 UTC
 == Auto-comment from SVN commit #29822 to the slim repo by ayoung ==
 == https://svn.slimdevices.com/slim?view=revision&revision=29822 ==

Fixed bug 15477: New track stream can get (superfluous) packets from old stream
Comment 4 Chris Owens 2010-04-08 17:24:11 UTC
This bug has been marked fixed in a released version of Squeezebox Server or the accompanying firmware or mysqueezebox.com release.

If you are still seeing this issue, please let us know!