Bug 3126 - rescan with Moodlogic enable causes 100% CPU forever
: rescan with Moodlogic enable causes 100% CPU forever
Status: RESOLVED DUPLICATE of bug 2830
Product: Logitech Media Server
Classification: Unclassified
Component: MoodLogic
: 6.5b1
: PC Windows Server 2003
: P2 major (vote)
: ---
Assigned To: Blackketter Dean
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2006-03-07 16:34 UTC by Greg Hamilton
Modified: 2006-03-10 20:24 UTC (History)
0 users

See Also:
Category: ---


Attachments
copy of log, slimserver.pref and slimserver.db (4.79 MB, application/octet-stream)
2006-03-10 19:19 UTC, Greg Hamilton
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Greg Hamilton 2006-03-07 16:34:32 UTC
Running latest nightly 6.51b, build 6531
Music library is approx 24,000 tracks.

I have been noticing for a while the rescans seeming to never complete.  I would just restart slimserver and on my merry way.  However I was updating the library this weekend and I noticed it taking over 2 days (48 hours) to scan.  If I disable the moodlogic plug-in the problem goes away.

I have tested against slimserver 6.22 and it does not have the problem.

I have notices that a manual clean & scan, takes off like it's suppose to but sometime later (Maybe 5 minutes it starts to choke.)

Please let me know if there is anything I can enable to help debug.
Comment 1 KDF 2006-03-07 17:49:02 UTC
are you sure it is moodlogic and not musicmagic?

moodlogic hasn't changed in a VERY long time.
Comment 2 KDF 2006-03-07 18:05:26 UTC
if you are certain, the please try a scan with d_moodlogic d_import d_info and check the log.
Comment 3 Greg Hamilton 2006-03-10 19:19:43 UTC
Created attachment 1164 [details]
copy of log, slimserver.pref and slimserver.db

KDF,

I've done some more testing and there appears to only be a problem if a audio dir is specified and moodlogic is enabled. The logs don't show cpu%, but a few minutes into the scans cpu pegs out and disk activity become very minimal.

Greg
Comment 4 KDF 2006-03-10 20:24:43 UTC
thanks.  in that case, this would seem to be the same conditions as bug 2830.  i am testing Dan's improved fix and it looks good so far.  

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