Bug 1141 – crash when hitting Now Playing after changing buffer fullness settings in web interface

Bug 1141 - crash when hitting Now Playing after changing buffer fullness settings in web interface

Summary:

crash when hitting Now Playing after changing buffer fullness settings in web...

Status:	CLOSED FIXED

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

Importance:	P2 normal (vote)
Target Milestone:	---
Assigned To:	Blackketter Dean

URL:
Keywords:

Depends on:
Blocks:
	Show dependency tree / graph

Reported:	2005-03-21 10:25 UTC by Kevin Pearsall
Modified:	2008-12-15 11:57 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 Kevin Pearsall 2005-03-21 10:25:14 UTC

Use of uninitialized value in multiplication (*) at
/Users/kpearsall/6/server/Slim/Player/SqueezeboxG.pm line 65.
Use of uninitialized value in multiplication (*) at
/Users/kpearsall/6/server/Slim/Player/Squeezebox2.pm line 183.
Can't use an undefined value as an ARRAY reference at
/Users/kpearsall/6/server/Slim/Player/Squeezebox2.pm line 217.
2005-03-21 10:18:53.2545 Got to the END.
2005-03-21 10:18:53.2554 Got sigint.
2005-03-21 10:18:53.2562 SlimServer cleaning up.


STR:
(using sb2 and latest trunk)
- set show buffer fullness to show up in playing display mode
- set Now Playing Information to Show Buffer Fullness
- on now playing screen, hit the now playing button

Comment 1 Vidur Apparao 2005-03-21 12:39:39 UTC

See bug 985 for an explanation of what's happening. kdf to commit a fix.

Comment 2 KDF 2005-03-21 19:04:41 UTC

committed to r2640

Comment 3 Kevin Pearsall 2005-03-22 10:59:20 UTC

verified in r2651

Comment 4 James Richardson 2008-12-15 11:57:19 UTC

This bug has been fixed in the latest release of SqueezeCenter!

Please download the new version from http://www.slimdevices.com/su_downloads.html if you haven't already.  

If you are still experiencing this problem, feel free to reopen the bug with your new comments and we'll have another look.