Slim.exe 6.2b1 bld 3774 crashing on rescan of playlist

[MrC]

Slim.exe is crashing upon rescan of playlist.

Version: 6.2b1 - 3774 - Windows XP - EN - cp1252

[Dan Sully]

* MrC shaped the electrons to say...

>Slim.exe is crashing upon rescan of playlist.
>
>Version: 6.2b1 - 3774 - Windows XP - EN - cp1252

You're some days behind - this should be fixed in the latest nightly.

-D
--
<faisal> my life is collapsing to what will soon be NEGATIVE INTEGER degrees of separation.

[MrC]

I'm not sure what happened then, I downloaded and installed the 8-02 nightly, and the report was against that build. I'm downloading the 8-03 nightly now, and will report back.

[max.spicer]

I had this problem running the nightly that I downloaded at about 8:30pm last night (via svn). The server crashed every time I did a rescan. I sorted it by doing a "wipe cache" then a rescan.

Max

* MrC shaped the electrons to say...

>Slim.exe is crashing upon rescan of playlist.
>
>Version: 6.2b1 - 3774 - Windows XP - EN - cp1252

You're some days behind - this should be fixed in the latest nightly.

-D
--
<faisal> my life is collapsing to what will soon be NEGATIVE INTEGER degrees of separation.

[MrC]

Well, now I've updated to the 8-03 nightly. I'm getting asked to updated firmware (for the new WoL addition), so I know its the latest.

Still, the version shows on the web page under Settings shows:

SlimServer Version: 6.2b1 - 3774 - Windows XP - EN - cp1252

and there's no version in Properties for slim.exe. Where do I find the version? Perhaps the web page version needs to be updated with the nightly builds as well.

[kdf]

Quoting "max.spicer" <max.spicer.1t93gp (AT) no-mx (DOT) forums.slimdevices.com>:

>
> I had this problem running the nightly that I downloaded at about 8:30pm
> last night (via svn). The server crashed every time I did a rescan. I
> sorted it by doing a "wipe cache" then a rescan.

"the server crashed" is fairly useless info, to be honest. Everyone loading up
nightly builds each day really should be making themselves aware of how to
check the logs/event viewer for more specific info. Any crash should create an
entry in the Windows Event Viewer (for those running the EXE). The rest need
to run command line and watch the terminal, or use the --logfile commandline
option. Even windows users might want to try this with the exe from time to
time if the event viewer doesn't happen to show any crash entry.

this would save a lot of "well, we fixed one possible crash, try it now"
reponses.

cheers,
kdf

[MrC]

Wow, hold on there Dick Tracy! :-)

There's nothing wrong whatsoever with simple "server crashed" reports iff the problem is trivial to reproduce as indicated. Its one thing if reproducing it is not obvious or reliable; its another when one trial produces the crash. Sorry, but I've been in the biz a *long* time, developing and debugging unix kernels or other higly complex software. To often developers push back to get "more information" when often much of that information is non-essential.

But since you asked, here's the info:

The description for Event ID ( 0 ) in Source ( Application ) cannot be found. The local computer may not have the necessary registry information or message DLL files to display messages from a remote computer. You may be able to use the /AUXSOURCE= flag to retrieve this description; see Help and Support for details. The following information is part of the event: Can't call method "id" on an undefined value at /PerlApp/Slim/DataStores/DBI/DBIStore.pm line 767.

This turns out to be the same as:

http://forums.slimdevices.com/showthread.php?t=15518

I did not catch that they were the same bug, as the version number reported in that bug vs. what I tought was the correct vresion number did not match (the one shown at the bottom of the Server Settings page are incorrect, and don't seem to change).

[kdf]

On 4-Aug-05, at 12:26 PM, MrC wrote:

>
> Wow, hold on there Dick Tracy! :-)
>
> There's nothing wrong whatsoever with simple "server crashed" reports

I didn't say it was wrong, I said it wasn't useful.
>
if you want to have something fixed, it is always better to provide
details. Otherwise all teh dev's are left guessing while ppl bark to
have things fixed, and bitch about the constant crashes. And I'm not
the only one getting tired to the moaning, and also having to repeat
the same requests for info every time.

>
> But since you asked, here's the info:
>
>>
>> The description for Event ID ( 0 ) in Source ( Application ) cannot be
>> found. The local computer may not have the necessary registry
>> information or message DLL files to display messages from a remote
>> computer. You may be able to use the /AUXSOURCE= flag to retrieve this
>> description; see Help and Support for details. The following
>> information is part of the event: Can't call method "id" on an
>> undefined value at /PerlApp/Slim/DataStores/DBI/DBIStore.pm line 767.
> .
cool, thanks. I believe this one should be fixed in the very latest.
line 1502 is another crasher, that is still there.

see, much easier with info.

-kdf

[MrC]

Yup, confirmed fixed.

Now how about an answer to where I get the version number for slim.exe ? Pretty Please?

[kdf]

Quoting MrC <MrC.1t99hc (AT) no-mx (DOT) forums.slimdevices.com>:

>
> Yup, confirmed fixed.
>
> Now how about an answer to where I get the version number for slim.exe
> ? Pretty Please?

that I don't know. Mine always says "trunk", which I believe is expected if you
run from teh svn checkouts. The answer for this could require a long look at
the build process for the exe downloads. Does this build number stick even if
you uninstall the previous nightly before installing the latest?

-kdf