Bug 6382 – 7.0a1 causes computer to slow down and run at 100% CPU load.

Bug 6382 - 7.0a1 causes computer to slow down and run at 100% CPU load.

Summary:

7.0a1 causes computer to slow down and run at 100% CPU load.

Status:	RESOLVED WORKSFORME

Product:	Logitech Media Server
Classification:	Unclassified
Component:	Misc
Version:	7.0
Platform:	PC Windows XP

Importance:	P2 normal with 1 vote (vote)
Target Milestone:	---
Assigned To:	Unassigned bug - please assign me!

URL:
Keywords:

Depends on:
Blocks:
	Show dependency tree / graph

Reported:	2007-12-16 13:21 UTC by Wee Sim
Modified:	2007-12-18 10:15 UTC (History)
CC List:	1 user (show)

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 Wee Sim 2007-12-16 13:21:12 UTC

Hello,

I recently installed SqueezeCenter 7.0a1 because 6.5.5 and 6.5.4 did not work to resolve my playlist issues (duplicate song titles in albums). 

SqueezeCenter 7.0a1 resolved duplicate song titles, which was great, but it also slowed down my computer after synching with my Squeezebox 3 for not more than 5 minutes. Everything starts to massively get saturated by the SqueezeCenter and my CPU load shows 100%.

I am running an Intel Dual Core 2.00 GHz T2500 with 1.00 GB of RAM. I don't see how my computer specifications can be the cause.

I have tried SqueezeCenter on Opera and Internet Explorer, leaving the browsers open or not makes no difference to this saturation of CPU load.

Not sure what is going on because I feel that I am alone with this issue.

Thank you,
Wee Sim

Comment 1 Michael Herger 2007-12-17 00:34:33 UTC

Which process is using the CPU? Did you leave it finish its initial scan?

Comment 2 Wee Sim 2007-12-17 20:07:34 UTC

Hi,

I've tried the latest build 12-17 7.0a1 and the problem doesn't seem to reenact itself.

Either I was mistaken, or this issue has been solved.

Both ways, it's a good outcome.

-Wee Sim

Comment 3 Wallace Lai 2007-12-18 09:46:16 UTC

This probably should be marked as "Unreproducible" instead of "Invalid".  The bug is quite valid.  It could have been a one time bug or intermittent bug.