Bug 1057 – Softsqueeze2 should play nicer with SlimServer 5.4 and 6.0

Bug 1057 - Softsqueeze2 should play nicer with SlimServer 5.4 and 6.0

Summary:

Softsqueeze2 should play nicer with SlimServer 5.4 and 6.0

Status:	RESOLVED FIXED

Product:	Logitech Media Server
Classification:	Unclassified
Component:	Softsqueeze
Version:	6.0.0
Platform:	All All

Importance:	P2 normal (vote)
Target Milestone:	---
Assigned To:	Dan Sully

URL:
Keywords:

Depends on:
Blocks:
	Show dependency tree / graph

Reported:	2005-03-12 11:56 UTC by Dan Sully
Modified:	2008-09-15 14:37 UTC (History)
CC List:	0 users

See Also:
Category:	---

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.

Description Dan Sully 2005-03-12 11:56:50 UTC

Softsqueeze2 sends bad information to 5.4, which was causing it to crash. I've
fixed that bug, but SS2 should behave better, perhaps printing an error message
and refusing to connect.

SS2 also has a behavior when SlimServer isn't running to chew on CPU. Some sort
of backoff mechanism should be implemented so this doesn't happen.

Comment 1 Richard Titmuss 2005-03-13 15:05:16 UTC

I have added a message and stopped Softsqueeze2 from connecting to slimserver 5.4.x.

I don't see the cpu problem, do you know how you triggered it?

Comment 2 Dan Sully 2005-03-13 15:15:07 UTC

On OSX, when SoftSqueeze is running, but SlimServer isn't.

Comment 3 Richard Titmuss 2005-03-21 15:23:54 UTC

Dan, sorry but I still don't see this. Even tried on OSX :). How do you start
Softsqueeze, from the console or via webstart?

If you get chance (and I understand if not!) could you start Softsqueeze from
the console and capture a few stack traces with 'Ctrl-Break' a few seconds
apart. I should be able to see what's spinning from this.

Comment 4 Dan Sully 2005-03-22 15:47:13 UTC

Looks like this is no longer an issue, or my machine was in a wierd state.

Comment 5 Chris Owens 2006-06-16 14:41:04 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.