Bugzilla – Bug 868
browse by album crashes slimserver
Last modified: 2008-09-15 14:37:04 UTC
Using the web interface, browse by Album crashes the server. I am able to browse by album using the remote & softsqueeze. I've tested this using the default, exbrowse2 and fishbone skins. Logs show: 2005-02-25 23:21:50.6874 Scanning with 0 import plugins Malformed UTF-8 character (unexpected continuation byte 0xb0, with no preceding start byte) in transliteration (tr///) at C:/Program Files/slimperl/trunk/server/Slim/Utils/Text.pm line 34. currently running svn revision 2231
that message is usually an annoying warning, but doesn't end the server. Is there a final message?
That's it. The server was started with --d_info, --d_moodlogic, and --d_scan.
Gregory - could you possibly run the server using the perl debugger? perl -d slimserver.pl And then hit 'n' a few times - for next. That will start the server running. When it crashes, it should print out more information. Thanks.
Windows event manager shows: Faulting application perl.exe, version 5.8.4.810, faulting module msvcrt.dll, version 7.0.2600.1106, fault address 0x00033306. For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
Created attachment 281 [details] perl debugger log file Here is the output from the -d perl debugger
Thanks Greg - I just checked in what I hope is a fix for you. If you could update your svn tree and check. Thanks.
Dan, After updating the tree I am still getting the errors. I found a new version of activestate perl, so I updated to 5.8.6.811 from 5.8.6.810. It also has the same problem.
Additional observations. Deleted database started server, with moodlogic enabled and no autodir defined During the scan, I was able to browse albums using the web interface. Once the scan was completed and the server was idle I wasn't able.
Greg - can you upload the slimserversql.db file to this bug?
Created attachment 282 [details] zipped up slimserversql.db Here you go
Fix checked in as svn change #2250.
There are 536 bugs in the database with targets of '---' that were fixed prior to new year 2006. I am setting them to targets of 6.2.1 to keep them from showing up in my queries.