Bug 959 - Softsqueeze uses 100% CPU time
: Softsqueeze uses 100% CPU time
Status: RESOLVED FIXED
Product: Logitech Media Server
Classification: Unclassified
Component: Softsqueeze
: 6.0.0
: PC Windows XP
: P2 normal (vote)
: ---
Assigned To: Richard Titmuss
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2005-03-07 03:07 UTC by James Craig
Modified: 2008-09-15 14:37 UTC (History)
1 user (show)

See Also:
Category: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description James Craig 2005-03-07 03:07:15 UTC
As reported last week on mailing list by myself:
I also seem to be having a problem that sometimes when Softsqueeze is
running and songs change, something thrashes my PC.
I have been unable to further diagnose this because the computer becomes
completely unusable and I usually have to pull the plug out!
But, every time it has occurred I have recently started Softsqueeze and
have v6.0 running and a song has just finished. 

and also Chris Townsend:
With the 6.0 branch my softsqueeze clients that are remote from the server
consume 100% cpu (on the machine running the softsqueeze) when they reach
the end of the playlist.  This started happening when I went to the 6.0
branch.  I get the message that softsqueeze is written for server 5.4 and
I'm running 6.0 when I connect.  My softsqueeze is 1.17 which looks like the
newest I can get.  Let me know if there's any debugging I can turn on for
the client to give more info.  Thanks.
Comment 1 Chris 2005-03-08 01:23:00 UTC
In the last couple of weeks, I've also had the problem of 100% processor load
whenever I press "play" within Softsqueeze. I tracked it down to the fact that
I'm using the Java MP3 plugin as the MP3 decoder - if I revert to using JLayer
instead, the problem goes away.

The Java MP3 plugin used to work fine, so I'm not sure exactly what's changed...
Comment 2 Dan Sully 2005-03-09 16:14:38 UTC
A fix for the OFFSET bug has been checked in as Subversion change 2390.
Comment 3 Chris 2005-03-10 03:59:57 UTC
Thanks Dan - this fix works for me.
Comment 4 Chris Owens 2006-06-16 14:41:01 UTC
There are 536 bugs in the database with targets of '---' that were fixed prior to new year 2006.  I am setting them to targets of 6.2.1 to keep them from showing up in my queries.