Bug 15931 – Multiple players encounter PROBLEM: CAN'T OPEN FILE FOR: and then TinySC kills itself

Bug 15931 - Multiple players encounter PROBLEM: CAN'T OPEN FILE FOR: and then TinySC kills itself

Summary:

Multiple players encounter PROBLEM: CAN'T OPEN FILE FOR: and then TinySC kill...

Status:	RESOLVED DUPLICATE of bug 15821

Product:	SB Touch
Classification:	Unclassified
Component:	TinySC
Version:	7.5.0
Platform:	PC Windows XP

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

URL:
Keywords:

Depends on:
Blocks:
	Show dependency tree / graph

Reported:	2010-03-20 09:23 UTC by Mickey Gee
Modified:	2010-03-21 00:44 UTC (History)
CC List:	3 users (show)

See Also:
Category:	---

Attachments
Boom with error message (95.40 KB, image/jpeg) 2010-03-20 09:24 UTC, Mickey Gee	Details
SB3 with error message (61.00 KB, image/jpeg) 2010-03-20 09:25 UTC, Mickey Gee	Details
Second Boom with error message (92.33 KB, image/jpeg) 2010-03-20 09:26 UTC, Mickey Gee	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 Mickey Gee 2010-03-20 09:23:02 UTC

Watched this happen after 15 hours:

1. Two IP3K players in PROBLEM: CAN'T OPEN FILE FOR: state
2. 15 minutes later, another IP3K player has message on screen.
3. 15 minutes after that, Fab4 displays the generic "Having problems with ..." TinySC message. If you look at the the status screen, it's no longer running.

Just lucky to see this sequence. May have happened before, but I would scratch my head and wonder why.

This is with a Fab4/TinySC running version of firmware r8658. It's with 4 IP3K players (2 Boom, 2 SB3). Note that in this bug, one IP3K player did not encounter the CAN'T OPEN FILE issue. All players streaming MP3 files (Harry Potter Audio CD -- different book for each player).

Also used WD 1.5TB USB self-powered drive, which was involved in bug 15915 and could be problematic in some way.

The logs were useless since I turned on a bunch of wrong debug switches (UI).

Enclosing photos of 3 players with the aforementioned error message.

Comment 1 Mickey Gee 2010-03-20 09:24:32 UTC

Created attachment 6673 [details]
Boom with error message

Comment 2 Mickey Gee 2010-03-20 09:25:33 UTC

Created attachment 6674 [details]
SB3 with error message

Comment 3 Mickey Gee 2010-03-20 09:26:13 UTC

Created attachment 6675 [details]
Second Boom with error message

Comment 4 Alan Young 2010-03-21 00:44:44 UTC

There is not yet a Fab4 build incorporating TinySC r30394, which is needed for the fix to bug 15821. Trunk SbS r30393 also has the fix.

Note that the route cause of the problem (the trigger) is almost certainly a (transient) network failure.

I have just checked in a change to force a fab4 rebuild, so r8861 should include TinySC with the fix.

*** This bug has been marked as a duplicate of bug 15821 ***