Bug 3578 - Rhapsody imported M4A track crashes Slimserver on scan of library
: Rhapsody imported M4A track crashes Slimserver on scan of library
Status: CLOSED FIXED
Product: Logitech Media Server
Classification: Unclassified
Component: Rhapsody UPnP
: 6.2.2
: PC Other
: P2 normal (vote)
: ---
Assigned To: Dan Sully
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2006-06-15 16:47 UTC by Dan Evans
Modified: 2008-09-15 14:38 UTC (History)
0 users

See Also:
Category: ---


Attachments
M4A file crashes Slimserver when scanned (6.74 MB, application/octet-stream)
2006-06-15 16:52 UTC, Dan Evans
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Dan Evans 2006-06-15 16:47:24 UTC
(reference tmid 4968)  from customer:

when I attempt to play any of my Rhapsody imported M4a files through the Squeezebox (v3) I get a "Problem: Can't open file" error on the display.

When I try to scan the file he sent me, my Slimserver crashes instantly.  This happens on 6.2.2 and 6.3.0.

I've attached the file.
Comment 1 Dan Evans 2006-06-15 16:52:52 UTC
Created attachment 1265 [details]
M4A file crashes Slimserver when scanned

iTunes can play this file, as can Get Info on a Mac.  It also plays in WinAmp in XP.
Comment 2 KDF 2006-06-15 17:09:22 UTC
I get this in 6.5 (no slimserver crash, since scanner takes the hit...)

2006-06-15 17:05:56.2681 ERROR: readTags: While trying to ->getTag(D:\music\test\10 - Pressed In A Book.m4a) : Can't use string ("10") as an ARRAY ref while "strict refs" in use at
 D:\slim\server\CPAN/MP4/Info.pm line 383.

something isn't happy in the track number.


Comment 3 Chris Owens 2006-06-15 17:14:19 UTC
KDF beat me to it, but in just for thoroughness in 6.3 I get the crash, with the (now-unsurprising) error of:

Can't use string ("10") as an ARRAY ref while "strict refs" in use at C:\Program Files\SlimServer\server\CPAN/MP4/Info.pm line 383.
Comment 4 Blackketter Dean 2006-06-20 11:44:54 UTC
dan: what do you thinK?
Comment 5 Dan Sully 2006-06-21 11:11:09 UTC
Fixed in change 8074
Comment 6 Chris Owens 2006-06-27 14:21:51 UTC
This bug fix is now part of a released version, and so has been marked closed. If you are still experiencing this problem, please reopen the bug.