Bug 14347 – Software Updates run extremely slowly, then hang @ 99%?

Bug 14347 - Software Updates run extremely slowly, then hang @ 99%?

Summary:

Software Updates run extremely slowly, then hang @ 99%?

Status:	VERIFIED FIXED

Product:	SB Radio
Classification:	Unclassified
Component:	Setup
Version:	Include FW version in comment
Platform:	PC Other

Importance:	P2 normal (vote)
Target Milestone:	7.4.1
Assigned To:	Squeezebox QA Team email alias

URL:
Keywords:

Depends on:
Blocks:
	Show dependency tree / graph

Reported:	2009-09-27 12:42 UTC by Matt Wise
Modified:	2009-10-21 22:24 UTC (History)
CC List:	3 users (show)

See Also:
Category:	---

Attachments
The log was collected while baby was stuck at 99 percent (3.61 KB, text/plain) 2009-09-28 10:52 UTC, Ryan	Details
View All 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 Matt Wise 2009-09-27 12:42:01 UTC

I have only just started seeing this, but the last 3 software updates offered to my Baby (all while it was playing music) have run in super slow-motion. They take 15-20 minutes to get to 99%, then hang. Hard resets solve the issue.

Comment 1 Erland Isaksson 2009-09-27 22:27:49 UTC

I've seen the same thing on my Touch but not during the recent updates.

Comment 2 Ryan 2009-09-28 10:52:41 UTC

Created attachment 5945 [details]
The log was collected while baby was stuck at 99 percent

The log was collected while baby was stuck at 99 percent

Comment 3 Ross Levine 2009-09-28 11:37:55 UTC

I've seen this once too.

Comment 4 Chris Owens 2009-10-12 10:05:27 UTC

Felix notes it might be related to a memory leak that Tom fixed.  The fix is in

Comment 5 James Richardson 2009-10-12 16:11:27 UTC

QA to verify the issue has been addressed in 7.4.1 firmware

Comment 6 James Richardson 2009-10-13 12:50:26 UTC

tested r7847 several times, looks like this issue has been addressed

Comment 7 Stefan Hansel 2009-10-21 22:24:32 UTC

I was on 4.7.1 FW 7907.
The problem turned up again this morning.

Please reopen the bug !